THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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 following diagram shows a node running YARN Node Manager as a Mesos Slave task.
High Level Design
...
The following diagram shows a scenario where Mesos is used as the resource manager for a data center which allows both Mesos and YARN to schedule tasks on any node.
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 makes a decision to launch a new Node Manager.
- Myriad passes the required configuration and task launch information to the Mesos Master which forwards that to the Mesos Slave(s).
- Mesos Slave launches Myriad Executor which manages the life cycle of the Node Manager.
- 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.
- The YARN Node Manager, upon startup, advertises configured resources to the YARN Resource Manager. In the previous following 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.
- The YARN Resource Manager can launch containers now, via this Node Manager. The launched containers are mounted under the configured cgroup hierarchy.
