[
https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15151397#comment-15151397
]
Daniel Zhi commented on YARN-4676:
----------------------------------
I am puzzled about the these 5 timeout junit tests
(org.apache.hadoop.http.TestHttpServerLifecycle ,
org.apache.hadoop.yarn.client.cli.TestYarnCLI etc). All of them PASS on my
local machine (with or without my patch) and I don't my code change in the
patch could cause the timeout error --- I am not sure the timeout errors are
related to my patch and how to fix them.
> Automatic and Asynchronous Decommissioning Nodes Status Tracking
> ----------------------------------------------------------------
>
> Key: YARN-4676
> URL: https://issues.apache.org/jira/browse/YARN-4676
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.8.0
> Reporter: Daniel Zhi
> Assignee: Daniel Zhi
> Labels: features
> Attachments: GracefulDecommissionYarnNode.pdf, HADOOP-4676.004.patch,
> HADOOP-4676.005.patch
>
>
> DecommissioningNodeWatcher inside ResourceTrackingService tracks
> DECOMMISSIONING nodes status automatically and asynchronously after
> client/admin made the graceful decommission request. It tracks
> DECOMMISSIONING nodes status to decide when, after all running containers on
> the node have completed, will be transitioned into DECOMMISSIONED state.
> NodesListManager detect and handle include and exclude list changes to kick
> out decommission or recommission as necessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
