[ https://issues.apache.org/jira/browse/YARN-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038264#comment-14038264 ]
Jian He commented on YARN-2074: ------------------------------- Seem to find a bug in ResourceManager#RMContainerPreemptEventDispatcher#handle(), the ApplicationAttemptId is the id of the attempt who creates the container. In work-preserving AM restart, the ApplicationAttemptId here should be the current active attemptId so that the preemption is charged against the current attempt instead of previous one. I can file a jira for this. > Preemption of AM containers shouldn't count towards AM failures > --------------------------------------------------------------- > > Key: YARN-2074 > URL: https://issues.apache.org/jira/browse/YARN-2074 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Reporter: Vinod Kumar Vavilapalli > Assignee: Jian He > Attachments: YARN-2074.1.patch, YARN-2074.2.patch, YARN-2074.3.patch, > YARN-2074.4.patch, YARN-2074.5.patch, YARN-2074.6.patch, YARN-2074.6.patch, > YARN-2074.7.patch, YARN-2074.7.patch, YARN-2074.8.patch > > > One orthogonal concern with issues like YARN-2055 and YARN-2022 is that AM > containers getting preempted shouldn't count towards AM failures and thus > shouldn't eventually fail applications. > We should explicitly handle AM container preemption/kill as a separate issue > and not count it towards the limit on AM failures. -- This message was sent by Atlassian JIRA (v6.2#6252)