THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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 Cgroups hierarchy, and so on) and then launches it. For example: In the previous following 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 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 Cgroup hierarchy.