Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
ClientRMProtocol exposes a getClusterNodes api that provides a report on all nodes in the cluster including their rack information.
However, this requires the AM to open and establish a separate connection to the RM in addition to one for the AMRMProtocol.
Attachments
Issue Links
- duplicates
-
YARN-1722 AMRMProtocol should have a way of getting all the nodes in the cluster
- Resolved
- is duplicated by
-
YARN-1062 MRAppMaster take a long time to init taskAttempt
- Resolved
-
YARN-1200 Provide a central view for rack topologies
- Resolved
-
MAPREDUCE-6592 MR ApplicationMaster is not supposed to resolve rack locality! It should ask RM or NN about the topology
- Resolved
- is related to
-
YARN-386 [Umbrella] YARN API Changes
- Open
-
YARN-1928 TestAMRMRPCNodeUpdates fails ocassionally
- Closed
- relates to
-
YARN-552 Expose resource metrics as part of YarnClusterMetrics
- Open