hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels
Date Fri, 08 Apr 2016 22:56:25 GMT

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

Wangda Tan commented on YARN-4855:
----------------------------------

Actually I think pulling running NM data from RM is a doable idea, it avoids modifying RMAdmin
protocol. Yes the approach adds more overhead to network. But in practice we don't need update
node partition very frequently before we have YARN-3409. And it will be only required when
--fail-on-unkown-nodes is specified.

Thoughts?

> Should check if node exists when replace nodelabels
> ---------------------------------------------------
>
>                 Key: YARN-4855
>                 URL: https://issues.apache.org/jira/browse/YARN-4855
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Tao Jie
>            Assignee: Tao Jie
>            Priority: Minor
>         Attachments: YARN-4855.001.patch
>
>
> Today when we add nodelabels to nodes, it would succeed even if nodes are not existing
NodeManger in cluster without any message.
> It could be like this:
> When we use *yarn rmadmin -replaceLabelsOnNode "node1=label1"*, it would be denied if
node does not exist.
> When we use *yarn rmadmin -replaceLabelsOnNode -force "node1=label1"* would add nodelabels
no matter whether node exists



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

Mime
View raw message