Type: New Feature
Affects Version/s: None
Fix Version/s: None
YARN is intended to be general purpose, but it is missing some features to be able to truly support long lived applications and long lived containers.
This ticket is intended to
- discuss what is needed to support long lived processes
- track the resulting JIRA.
|1.||RM Should have a way to update the tokens it has for a running application||Open||Unassigned|
|2.||Define a HDFS based repository that allows YARN services to share resources||Open||Unassigned|
|3.||Add parameter for YARN resource requests to indicate "long lived"||Open||Unassigned|
|4.||De-link container life cycle from the process and add ability to execute multiple processes in the same long-lived container||Open||Unassigned|
|5.||NMs to support rolling logs of stdout & stderr||Open||Unassigned|
|6.||provide (async) application lifecycle events to management tools||Open||Unassigned|
|7.||add ability for AM to attach simple state information to containers||Open||Unassigned|
Vinod Kumar Vavilapalli made changes -
|Summary||Roll up for long lived YARN||Roll up for long-lived services in YARN|