[
https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429084#comment-15429084
]
Hudson commented on YARN-4685:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10313 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10313/])
YARN-4685. Disable AM blacklisting by default to mitigate situations (wangda:
rev 2da32a6ef9edebd86ca9672d10ce35b5a46818cc)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
> Disable AM blacklisting by default to mitigate situations that application
> 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
> Attachments: YARN-4685-workaround.patch, YARN-4685.patch
>
>
> 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]
