hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4413) Nodes in the includes list should not be listed as decommissioned in the UI
Date Thu, 03 Dec 2015 04:28:11 GMT

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

Sunil G commented on YARN-4413:
-------------------------------

Hi [~templedf]
Thank you for raising this ticket.
As you mentioned, I could see that a node is moved from exclude to include list and performed
{{-refreshNodes}}. And this caused some counts still to be displayed in UI. But a restart
will help here to clear the metrics.

One point to note here. The way I see it, I do not think we can remove or reset this decommissioned
count directly by only seeing the include list. There can be cases where we would have done
{{graceful decommissioning}}, and this can add few nodes to decommissioned list which is not
one-to-one mapped with exclude list.
So I feel we could look both lists upon refresh and remove/add nodes based on the entries
in both files and from memory.

> Nodes in the includes list should not be listed as decommissioned in the UI
> ---------------------------------------------------------------------------
>
>                 Key: YARN-4413
>                 URL: https://issues.apache.org/jira/browse/YARN-4413
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>
> If I decommission a node and then move it from the excludes list back to the includes
list, but I don't restart the node, the node will still be listed by the web UI as decomissioned
until either the NM or RM is restarted.  Ideally, removing the node from the excludes list
and putting it back into the includes list should cause the node to be reported as shutdown
instead.
> CC [~kshukla]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message