Page History

...

The following diagram shows two resource managers running independently which results in a statically partitioned datacenter:

HTML Comment


Advertising Resources: Mesos Slave and YARN’s Node Manager

...

The following diagram gives an overview of how YARN can run along side Mesos:

HTML Comment


Each node in the cluster has both daemons, Mesos Slave and YARN Node Manager, installed. By default, the Mesos slave daemon is started on each node and advertises all available resources to the Mesos Master.

 

Myriad launches NodeManager as a task under Mesos Slave:

1. Myriad makes a decision to launch a new NodeManager.
   1. It passes the required configuration and task launch information to the Mesos Master which forwards that to the Mesos Slave(s).
   2. Mesos Slave launches Myriad Executor which manages the lifecycle of the NodeManager.
   3. Myriad Executor upon launch, configures Node Manager (for example, specifying CPU and memory to advertise, cgroups hierarchy, and so on) and then launches it. For example: In the previous diagram, Node Manager is allotted 2.5 CPU and 2.5 GB RAM.
2. NodeManager, upon startup, advertises configured resources to YARN's Resource Manager. In the previous example, 2 CPU and 2 GB RAM are advertised. The rest of the resources are used by the Myriad Executor and NodeManager processes to run.
3. YARN's Resource Manager can launch containers now, via this Node Manager. The launched containers are mounted under the configured cgroup hierarchy. 

 

HTML Comment
XREF: See [cgroups doc](cgroups.md) for more information.

 

...