[
https://issues.apache.org/jira/browse/YARN-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092895#comment-15092895
]
Jason Lowe commented on YARN-3102:
----------------------------------
I agree with Daniel's comments.
Rather than manually scanning the inactive nodes list, can we build an inactive
node instance using the registering node's host and try to remove it from the
set? Should be a lot quicker as the number of inactive nodes gets large.
For the tests, I really would like to avoid sleeps whenever possible. We
either are sleeping too long leading to wasted time during tests (Hadoop test
runs are far too long as it is) or we don't wait enough and the test fails.
They often lead to flaky tests as hosts get loaded during test runs, etc.
We're already using the drain dispatcher, can't we simply wait for the
dispatcher events to drain rather than rely on magical sleep times?
> Decommisioned Nodes not listed in Web UI
> ----------------------------------------
>
> Key: YARN-3102
> URL: https://issues.apache.org/jira/browse/YARN-3102
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.0
> Environment: 2 Node Manager and 1 Resource Manager
> Reporter: Bibin A Chundatt
> Assignee: Kuhu Shukla
> Priority: Minor
> Attachments: YARN-3102-v1.patch, YARN-3102-v2.patch
>
>
> Configure yarn.resourcemanager.nodes.exclude-path in yarn-site.xml to
> yarn.exlude file In RM1 machine
> Add Yarn.exclude with NM1 Host Name
> Start the node as listed below NM1,NM2 Resource manager
> Now check Nodes decommisioned in /cluster/nodes
> Number of decommisioned node is listed as 1 but Table is empty in
> /cluster/nodes/decommissioned (detail of Decommision node not shown)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
