[YARN-3116] [Collector wireup] We need an assured way to determine if a container is an AM container on NM

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 2.9.0, 3.0.0-alpha1
• Component/s: nodemanager, timelineserver
• Target Version/s: 2.8.0
• Assignee: Giovanni Matteo Fumarola
• Reporter: Zhijie Shen
• Created: 29/Jan/15 21:35
• Updated: 25/Oct/19 20:26
• Resolved: 11/Jul/15 02:04

Description

In YARN-3030, to start the per-app aggregator only for a started AM container, we need to determine if the container is an AM container or not from the context in NM (we can do it on RM). This information is missing, such that we worked around to considered the container with ID "xxxx_01" as the AM container. Unfortunately, this is neither necessary or sufficient condition. We need to have a way to determine if a container is an AM container on NM. We can add flag to the container object or create an API to do the judgement. Perhaps the distributed AM information may also be useful to YARN-2877.

Issue Links

• blocks: YARN-2884 Proxying all AM-RM communications
• breaks: YARN-4839 ResourceManager deadlock between RMAppAttemptImpl and SchedulerApplicationAttempt
• duplicates: YARN-3828 Add a flag in container to indicate whether it's an AM container or not
• is related to: YARN-2882 Add an OPPORTUNISTIC ExecutionType
• relates to: YARN-3030 [Collector wireup] Set up timeline collector with basic request serving structure and lifecycle