Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
This is the umbrella ticket to capture any and every API cleanup that we wish to do before YARN can be deemed beta/stable. Doing this API cleanup now and ASAP will help us escape the pain of supporting bad APIs in beta/stable releases.
Attachments
Issue Links
- is blocked by
-
YARN-85 Allow per job log aggregation configuration
- Open
-
YARN-352 Inconsistent picture of how a container was killed when querying RM and NM in case of preemption
- Open
-
YARN-221 NM should provide a way for AM to tell it not to aggregate logs.
- Resolved
-
YARN-1279 Expose a client API to allow clients to figure if log aggregation is complete
- Resolved
-
YARN-475 Remove ApplicationConstants.AM_APP_ATTEMPT_ID_ENV as it is no longer set in an AM's environment
- Closed
-
YARN-550 ContainerLaunchContext::getServiceData and setServiceData need a lot of clarification
- Resolved
-
YARN-662 [Umbrella] Enforce required parameters for all the protocols
- Open
- relates to
-
YARN-435 Make it easier to access cluster topology information in an AM
- Open
-
YARN-723 Yarn default value of physical cpu cores to virtual core is 2
- Closed
-
YARN-142 [Umbrella] Cleanup YARN APIs w.r.t exceptions
- Closed