[
https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231422#comment-15231422
]
Hudson commented on YARN-4756:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9576 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9576/])
YARN-4756. Unnecessary wait in Node Status Updater during reboot. (Eric (kasha:
rev e82f961a3925aadf9e53a009820a48ba9e4f78b6)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeManagerResync.java
> Unnecessary wait in Node Status Updater during reboot
> -----------------------------------------------------
>
> Key: YARN-4756
> URL: https://issues.apache.org/jira/browse/YARN-4756
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Eric Badger
> Assignee: Eric Badger
> Attachments: YARN-4756.001.patch, YARN-4756.002.patch,
> YARN-4756.003.patch, YARN-4756.004.patch, YARN-4756.005.patch
>
>
> The startStatusUpdater thread waits for the isStopped variable to be set to
> true, but it is waiting for the next heartbeat. During a reboot, the next
> heartbeat will not come and so the thread waits for a timeout. Instead, we
> should notify the thread to continue so that it can check the isStopped
> variable and exit without having to wait for a timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
