hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Jie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4855) Should check if node exists when replace nodelabels
Date Wed, 06 Apr 2016 07:04:25 GMT

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

Tao Jie commented on YARN-4855:

[~Naganarasimha], thanks for reply.
We are trying to split resource pool for certain Applications from our cluster by nodeLabel.
For example, we need a resource pool of 10 nodes, then we run a script with *rmadmin -replaceLabelsOnNode*
cmd. However, this command always run successfully even though nodes are not available in
cluster (node is down or misspelling of hostname). As a result, we should do something more
to ensure the capacity of the resource pool. So I hope this option may help.

> 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
>            Priority: Minor
> 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

View raw message