Client URI accepts hostname:port format, but ignores it


I'm fairly new to Alluxio and have just set up a cluster on DCOS. While trying to connect via the Java client, I noticed there was an option to enter the hostname and port in the AlluxioURI constructor.

val path = new AlluxioURI(s"alluxio://<remote master ip>:19998/test.csv");

However, it still tries to connect to a local instance in this case. After some digging (and some communication in the alluxio mailing list), I realized it is necessary to use an file within my project. This was not very clear and confusing since the URI accepts it, and even validates the format, but ignores it.

This functionality should either be enabled or removed and the documentation cleared up. As far as the documentation is concerned, it is not entirely clear that the same configuration file that the server uses should be used for the client as well.


Alluxio v1.2.0 server and Java client
DCOS/Marathon/Mesos cluster


Andrew Audibert
November 9, 2016, 8:16 PM

For this ticket we should raise an error if an Alluxio URI uses a hostname/port that is different from the hostname/port in the Alluxio configuration. If you're interested please take it and I'll be happy to review.

In the long run we'll want to respect the hostname/port specified in the URI, but the current system assumes in many places that there is only one Alluxio master, so it will take some significant work.

Sergey Chernolyas
November 12, 2016, 8:21 AM

Ok. I will try to fix it.

Calvin Jia
November 22, 2016, 6:38 PM

How's the progress on this, would you like any opinions on your approach?

Sergey Chernolyas
November 22, 2016, 7:08 PM

I did nothing for the task. I haven't time for working in the project yet

Zac Blanco
September 10, 2018, 5:02 PM

This should be taken care of now. See


Zac Blanco


Kyro Hale


Epic Link


Fix versions

Affects versions