The problem with using the public hostname everywhere is that it's not the hostname the machine reports for itself, so applications running on Mesos that care about data placement, such as Spark and Hadoop, will not know which data is on the node. (That is, HDFS will see the node as ec2-foo.internal, and Mesos will say it's ec2-bar.amazonaws.com. If you wanted to use a single hostname, you'd have to use the internal one and lose the usability for EC2.
However, I don't see what would be wrong with just having a webui_url property on each slave. That could then use the public hostname and incorporate the port as well. Matei On Aug 17, 2011, at 7:58 PM, Benjamin Hindman wrote: >> No, up until now I haven't specified a webui_port ... > > Yeah, that's what I expected (given the TODO in the code). The first work > around will be using webui_port=8081 for your slaves. However, this doesn't > explain why the slave webui isn't loading. But, if you can drop the result of > doing: > > $ curl http://slave_hostname:port/slave/state.json > > Then I can try and debug why that JSON doesn't appear to be getting generated > correctly. > >> I believe that talking to public addresses instead of private ones means you >> pay for the traffic ... > > > This sounds like it's just across availability zones, and that you would pay > for the traffic across availability zones regardless of if you used a private > or a public address. > > > Thanks Michael! > > > >> >> Michael >
