Elizabeth Lingg

The hdfs-site.xml will not be different if you use Mesos DNS, because the Mesos DNS names will resolve to the new tasks.

You need to use HDFS with Mesos DNS enabled, see the instructions here: https://github.com/mesosphere/hdfs#mesos-dns-custom-configuration.

@tangzhankun, yes, and in that case even if the namenode1 relocates, it doesn't matter because Mesos DNS will resolve it to the host where it relocated.

It is implemented. Please see the instructions for running with Mesos DNS and try it out!

Yes, it is! In fact, we use the Mesos DNS version for DCOS! Use the example config files here, https://github.com/mesosphere/hdfs/tree/master/example-conf/mesosphere-dcos. You may need to make a few more modifications to...

Sure, glad to help! It will populate these config files if you place these config files under etc/hadoop/ before building and running your code.

Sure, @tangzhankun, You should set the mesos DNS names in hdfs-site.xml and mesos-site.xml. This discussion is best done offline. Could you please send me an email to follow up?

@abhay-agarwal, Actually they are referring to distributing core-site.xml with configserver so it picks up the environment variables which we don't yet do.

Note there is a security conern with using these parameters so we may not want these defined by default. Per @brndnmtthws "One other note: you may not want to define...

Talked to @rmvz, and he is not using the parameter for block based storage in order to avoid touching other resources by using "fs.s3n.aws" instead of “fs.s3.aws.”