Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Launching the Myriad Environment

To start Myriad, run the YARN daemon from the command line:

Code Block
yarn-daemon.sh start resourcemanager

 

To shut down Myriad, run the YARN daemon from the command line:

Code Block
yarn-daemon.sh stop resourcemanager

 

Alternatively, start and stop Myriad from the Marathon UI. See Marathon: Application Basics for more information. For example, create an application to start the Resource Manager:

Code Block
 cd hadoop-2.7.1/sbin && yarn-daemon.sh start resourcemanager

 

Launching the Myriad Environment

The Myriad environment is established by running an initial application for the resource manager. This initial application name is specified in the yarn-site.xml file with the the yarn.resourcemanager.hostname property and the value, <app-ID>.<framework>.mesos.

For example, if the value of  yarn.resourcemanager.hostname property is rm.marathon.mesos:

  • rmThe ID given to the Resource Manager when launched using Marathon. Mesos-DNS constructs the Resource Manager hostname using the ID.
  • marathon - The Mesos framework

If you are using Marathon, launch Marathon and run an initial Resource Manager application. See Starting Resource Manager for more information.


Ports

The ports used by Mesos, Marathon, and Myriad areThe Myriad environment is launched and monitored by starting the Mesos, Marathon, and Myriad applications using the following ports:

ApplicationPortSyntax
Marathon8080http://<IP address>:8080
Mesos5050http://<IP address>:5050. Use the 5050 port and Frameworks directory. For example: http://<ip <IP address>:5050/#/frameworks (http://10.141.141.20:5050/#/frameworks)
Myriad8192

http://<IP address>:8192. For example: http://<ip <IP address>:8192/ (http://10.141.141.20:8192/)

  • Without the Mesos-DNS service, this IP is slave node's IP address where the ResourceManager Resource Manager is running.
  • With the Mesos-DNS service, Mesos-DNS discovers the node where the ResourceManager is Resource Manager is running by using Mesos DNS FQDN (<app><app-name>.<framework>.mesos).