[ 
https://issues.apache.org/jira/browse/YARN-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kuhu Shukla updated YARN-3102:
------------------------------
    Attachment: YARN-3102-v1.patch

This patch adds semi-dummy <NodeID,RMNode> entries to active RMNodes map on 
init() for all nodes in the exclude list. Such a node is then transitioned 
right away to DECOMMISSIONED state from NEW state. Also, to fix the metric 
discrepancy if such a node joins back, the AddNodeTransition is modified. A 
simple test case is included.

Another approach can instead add the functionality of making transitions on 
inactiveRMNodes as well. This would allow not adding such dummy nodes to active 
list in the first place and put it in the inactive list instead.

> 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
>
>
> 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)

Reply via email to