So my last weird issue may be a MapR specific issue, but I wanted to lay it out here because it's odd. If you recall, I was talking about the mapr.host not being correct and that was causing some "issues" in that when the nodemanager tried to run, it would use the wrong hostname for the locality of the shuffle volumes. I addressed that specific issue with setting the mapr.host to be the hostname using
yarnEnvironment: YARN_HOME: hadoop-2.7.0 YARN_NODEMANAGER_OPTS: "-Dnodemanager.resource.io-spindles=4.0 -Dmapr.host=$(hostname -f)" in the Myriad config. This runs the hostname -f command and sets the mapr.host to be correct at run time. The weird thing is was that while the resourcemanager.hostname is correct from my yarn-site.xml yarn.resourcemanager.hostname myriad.marathon.mesos - yarn-site.xml There were a number of settings that were using the hostname of my box (and I found it came from the mapr.host through some testing, when I saw it it was using hostname -f, I ran it once with just hostname, and no FQDN in this setup, therefore these items are using mapr.host) that are related to the resource manager. Looking below, you can see that resourcemanager.address, resourcemanager.scheduler.address, resourcemanager.admin.address, resourcemanager.resource-tracker.address all seem to be being filled AFTER I set the the mapr.host, Yet, if you look at https://hadoop.apache.org/docs/r2.7.0/hadoop-yarn/hadoop-yarn-common/yarn-default.xml it states that it should be using yarn.resourcemanager.admin.address${yarn.resourcemanager.hostname}:8033 yarn.resourcemanager.hostname (I believe all of these settings are like this) for the settings, yet it's obviously using mapr.host instead. What components would be setting this? Overwriting the default? mapr.host is weird in that it's mapr only, but I thought I addressed that, and you can see that the conf shows yarn.resourcemanager.hostname to be correct, thus I am at loss here. In addition, the other strange thing is my node managers are working, I am not sure where these settings may hurt me, but I don't like that that they are obviously RM settings using the NM hostname, and while I don't see errors now, I am sure there will be errors at some point. Any thoughts on this would be welcome. Settings: (Note: UB stands for Ubuntu, it's which of my boxes this setting came from) The format is name UB: value - source yarn.resourcemanager.address UB: hadoopmapr5:8032 - programatically yarn.resourcemanager.hostname UB: myriad.marathon.mesos - yarn-site.xml yarn.resourcemanager.scheduler.address UB: hadoopmapr5:8030 - programatically mapr.host UB: hadoopmapr5.brewingintel.com - yarn.resourcemanager.admin.address UB: hadoopmapr5:8033 - programatically yarn.resourcemanager.resource-tracker.address UB: hadoopmapr5:8031 - programatically
