Hey John,
Are you trying to run the resource manager from the tar ball via marathon?
It's doable, my suggested approach would be to use a json like this:
{
"id": "resource-manager",
"uris": ["hdfs://namenode:port/dist/hadoop-2.7.0.tgz",
"hdfs://namenode:port/dist/conf/hadoop/yarn-site.xml",
"hdfs://namenode:port/dist/conf/hadoop/hdfs-site.xml",
"hdfs:///dist/conf/hadoop/core-site.xml",
"hdfs://namenode:port/dist/conf/hadoop/mapred-site.xml"],
"cmd": "cp *.xml hadoop-2.7.0/etc/hadoop && cd hadoop-2.7.0 && bin/yarn
resourcemanager",
"mem": 16,
"cpu": 1
"instances" : 1,
"user": "yarn"
}
Basically it keeps you from redoing the tar ball every time you edit a
config, instead you just upload the new yarn-site.xml. The Node Manager
gets it's config from the Resource Manager (I'm assuming this is all for
remote distribution, otherwise creating the tar ball is optional).
Darin
On Mon, Oct 5, 2015 at 2:36 PM, John Omernik <[email protected]> wrote:
> Hey all, I've been waiting until the chaos of the code move has died down.
> I am looking to get this working on my MapR cluster now, and would like
> some clarification on instructions here:
>
>
>
> https://cwiki.apache.org/confluence/display/MYRIAD/Installing+for+Administrators
>
> Basically, in the instructions below, it has the "remove the
> yarn-site.xml. Yet to run the resource manager with myriad, you need the
> yarn-site to be packaged with things (unless I am reading that incorrectly)
> Is the only option right now to created a tarball for nodemanagers, and
> have this be different from the tarball for the resource manager?
>
> Step 5: Create the Tarball
>
> The tarball has all of the files needed for the Node Managers and Resource
> Managers. The following shows how to create the tarball and place it in
> HDFS:
> cd ~
> sudo cp -rp $YARN_HOME .
> sudo rm $YARN_HOME/etc/hadoop/yarn-site.xml
> sudo tar -zcpf ~/hadoop-2.7.1.tar.gz hadoop-2.7.1
> hadoop fs -put ~/hadoop-2.7.1.tar.gz /dist
>
