Page History

...

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

Advertising Resources: Mesos Slave and

...

YARN Node Manager

The Mesos Slave and YARN’s YARN Node Manager are processes that run on the host OS. Both processes advertise available resources to Mesos Master and YARN’s YARN Resource Manager respectively. Each process can be configured to advertise a subset of resources. This ability is leveraged, in conjunction with cgroups, to allow Mesos Slave and YARN’s YARN Node Manager to co-exist on a node.

...

1. Myriad makes a decision to launch a new Node Manager.
   1. Myriad 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 life cycle of the Node Manager.
   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, the Node Manager is allotted 2.5 CPU and 2.5 GB RAM.
2. The YARN Node Manager, 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 Node Manager processes to run.
3. The YARN 's Resource Manager can launch containers now, via this Node Manager. The launched containers are mounted under the configured cgroup hierarchy.

...