[
https://issues.apache.org/jira/browse/YARN-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16401127#comment-16401127
]
Naganarasimha G R edited comment on YARN-8021 at 3/15/18 9:19 PM:
------------------------------------------------------------------
[~GergelyNovak] , we can use "failOnUnknownNodes" option to ensure that the
command fails if the node is invalid. we had not taken the approach which you
had mentioned because it will cause a incompatible change and earlier we wanted
to support to map a label even when the node is down or yet to be added to the
system.
Will close this Jira, if this option satisfies your requirement !
was (Author: naganarasimha):
[~GergelyNovak] , we can use "failOnUnknownNodes" option to ensure that the
command fails if the node is invalid. we had not taken the approach which you
had mentioned because it will cause a incompatible change and earlier we wanted
to support to map a label even when the node is down or yet to be added to the
system.
> The -addToClusterNodeLabels command doesn't provides error message for
> invalid node ID
> --------------------------------------------------------------------------------------
>
> Key: YARN-8021
> URL: https://issues.apache.org/jira/browse/YARN-8021
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Gergely Novák
> Priority: Major
>
> {noformat}
> yarn rmadmin -replaceLabelsOnNode "invalid-node-id:1234=node_label_x"
> {noformat}
> The above command doesn't return anything aside from the usual "Connecting to
> ResourceManager at..." message. It also doesn't print anything for a
> successful node label replacement, but it does throw an error for most of the
> other bad inputs (invalid port, invalid node label, invalid format).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
