[
https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Badger updated YARN-4756:
------------------------------
Description: 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. (was: The
Node Status Updater 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. )
> 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
>
>
> 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)
