hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3963) AddNodeLabel on duplicate label addition shows success
Date Tue, 28 Jul 2015 17:44:05 GMT

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

Sunil G commented on YARN-3963:

Thanks [~bibinchundatt] for the updated patch. +1 for same.
As mentioned by [~leftnoteasy] and [~Naganarasimha], its better to throw exception in client
side while we fail to update/add node label.
As I see it, I can see full exception stack trace in client side in this case (also in case
of other commands too) and its too verbose. I think we can make its compact and n it will
be more easily readable.  I ll file a separate ticket if its ok.

> AddNodeLabel on duplicate label addition shows success 
> -------------------------------------------------------
>                 Key: YARN-3963
>                 URL: https://issues.apache.org/jira/browse/YARN-3963
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>            Priority: Minor
>         Attachments: 0001-YARN-3963.patch, 0002-YARN-3963.patch, 0003-YARN-3963.patch,
> Currently as per the code in {{CommonNodeLabelManager#addToClusterNodeLabels}} when we
add same nodelabel again event will not be fired so no updation is done. 
> {noformat}
> ./yarn rmadmin –addToClusterNodeLabels x
> ./yarn rmadmin –addToClusterNodeLabels “x(exclusive=true)”
> ./yarn rmadmin –addToClusterNodeLabels “x(exclusive=false)”
>  {noformat}
> All these commands will give success when applied again through CLI 
> {code}
> 2015-07-22 21:16:57,779 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager:
Add labels: [<z:exclusivity=true>]
> 2015-07-22 21:16:57,779 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=dsperf   IP= OPERATION=addToClusterNodeLabels        TARGET=AdminService
> 2015-07-22 21:17:06,431 INFO org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager:
Add labels: [<z:exclusivity=false>]
> 2015-07-22 21:17:06,431 INFO org.apache.hadoop.yarn.server.resourcemanager.RMAuditLogger:
USER=dsperf   IP=<IP> OPERATION=addToClusterNodeLabels        TARGET=AdminService  
>  {code}
> Also since exclusive=true to false is not supported success is misleading

This message was sent by Atlassian JIRA

View raw message