Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Currently, YARN is implemented based on statefull single resource manager architecture. This approach can raise operation costs compare to stateless multi resource manager architecture, because we need to care which resource manager is active to ensure availability.
We can avoid this problem by saving all states into updatable and transactional RMStateStore such as ZooKeeper or RDBMS. If we take this approach, multiple resource managers can be launched at the same time. As a result, operation cost can be reduced, because we don't need to maintain specific(current master) resource manager.
This idea is based on a paper: “Omega: flexible, scalable schedulers for large compute clusters”[1].
[1] http://eurosys2013.tudos.org/wp-content/uploads/2013/paper/Schwarzkopf.pdf
Attachments
Issue Links
- is related to
-
YARN-149 [Umbrella] ResourceManager (RM) Fail-over
- Resolved