hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for "Decommissioned Nodes" field
Date Thu, 25 Sep 2014 04:22:34 GMT

    [ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147350#comment-14147350

Jian He commented on YARN-2523:

Patch looks good to me too.
YARN-1071 was done to make sure decommissioned count is consistent across RM restart, but
apparently causing more problems..

Not related to this jira, just to improve the previous testDecomissionedNMsMetricsOnRMRestart.
Maybe we can add the following before restarting 2nd RM so that the decommissioned count is
reset to 0 before 2nd RM restart, as I think in test both RM share the same ClusterMetrics
   // make sure decommissioned count is 0 2nd RM before restart.
    Assert.assertEquals(0, ClusterMetrics.getMetrics().getNumDecommisionedNMs());

    // restart RM.
    MockRM rm2 = new MockRM(conf);

> ResourceManager UI showing negative value for "Decommissioned Nodes" field
> --------------------------------------------------------------------------
>                 Key: YARN-2523
>                 URL: https://issues.apache.org/jira/browse/YARN-2523
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager, webapp
>    Affects Versions: 3.0.0
>            Reporter: Nishan Shetty
>            Assignee: Rohith
>         Attachments: YARN-2523.1.patch, YARN-2523.patch, YARN-2523.patch
> 1. Decommission one NodeManager by configuring ip in excludehost file
> 2. Remove ip from excludehost file
> 3. Execute -refreshNodes command and restart Decommissioned NodeManager
> Observe that in RM UI negative value for "Decommissioned Nodes" field is shown

This message was sent by Atlassian JIRA

View raw message