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

Wangda Tan updated YARN-2943:
-----------------------------
    Attachment: YARN-2943.2.patch

Hi [~jianhe],
Thanks for your comments,
bq. If I restart NM, “num of active NMs” is incorrect; this is probably because 
NM is using ephemeral ports;
This is what RM can see about NM, after some time elapsed, lost NM will be 
marked to "LOSTED", and will not count in RM side too.

bq. “<NO_LABEL>” -> “N/A”, similarly, update the previous nodes page to show 
“N/A” for not labeled nodes;
IMO, N/A is not clear enough. By wikipedia: http://en.wikipedia.org/wiki/N/a, 
N/a means "not available", "not applicable" or "no answer". Here no-label is 
just a kind of special label, since "NO_LABEL" has all same characteristics as 
other "normal" labels, like exclusivity, etc. 

bq. usability: <num of active NMs> link can point to a filtered list of nodes 
by label ?
It already did like what you suggested, when user/admin click the number, it 
will link to NM page and only shows NMs has that label. 

And I've addressed rest of your comments.

> Add a node-labels page in RM web UI
> -----------------------------------
>
>                 Key: YARN-2943
>                 URL: https://issues.apache.org/jira/browse/YARN-2943
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>         Attachments: Node-labels-page.png, Nodes-page-with-label-filter.png, 
> YARN-2943.1.patch, YARN-2943.2.patch
>
>
> Now we have node labels in the system, but there's no a very convenient to 
> get information like "how many active NM(s) assigned to a given label?", "how 
> much total resource for a give label?", "For a given label, which queues can 
> access it?", etc.
> It will be better to add a node-labels page in RM web UI, users/admins can 
> have a centralized view to see such information.



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

Reply via email to