[
https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282415#comment-15282415
]
Rohith Sharma K S commented on YARN-4685:
-----------------------------------------
Since this issue is introduced by YARN-2005 and committed to branch-2.8, should
YARN-2005 reverted as long as right solution is decided??. One biggest
challenge to revert is many patches are committed on top of YARN-2005.
OR should we go ahead with changing threshold to 0.2 default for 2.8 release?
Any thoughts
> AM blacklisting result in application to get hanged
> ---------------------------------------------------
>
> Key: YARN-4685
> URL: https://issues.apache.org/jira/browse/YARN-4685
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.8.0
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Priority: Critical
>
> AM blacklist addition or removal is updated only when RMAppAttempt is
> scheduled i.e {{RMAppAttemptImpl#ScheduleTransition#transition}}. But once
> attempt is scheduled if there is any removeNode/addNode in cluster then this
> is not updated to {{BlackListManager#refreshNodeHostCount}}. This leads
> BlackListManager to operate on stale NM's count. And application is in
> ACCEPTED state and wait forever even if blacklisted nodes are reconnected
> with clearing disk space.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
