Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 4 Nov 2016 19:46:58 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13018157.1478275619000.194047.1478288818872@Atlassian.JIRA>
In-Reply-To: <JIRA.13018157.1478275619000@Atlassian.JIRA>
References: <JIRA.13018157.1478275619000@Atlassian.JIRA> <JIRA.13018157.1478275619270@arcas>
Subject: [jira] [Commented] (YARN-5837) NPE when getting node status of a
 decommissioned node after an RM restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 04 Nov 2016 19:47:01 -0000


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

Jason Lowe commented on YARN-5837:
----------------------------------

Thanks for the patch!  My apologies for missing this when reviewing YARN-3102.

+1, both patches look good to me.  I'll commit these later today if there are no objections.

> NPE when getting node status of a decommissioned node after an RM restart
> -------------------------------------------------------------------------
>
>                 Key: YARN-5837
>                 URL: https://issues.apache.org/jira/browse/YARN-5837
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.3, 3.0.0-alpha1
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: YARN-5837.001.patch, YARN-5837.branch-2.7.001.patch
>
>
> If you decommission a node, the {{yarn node}} command shows it like this:
> {noformat}
> >> bin/yarn node -list -all
> 2016-11-04 08:54:37,169 INFO client.RMProxy: Connecting to ResourceManager at 0.0.0.0/0.0.0.0:8032
> Total Nodes:1
>          Node-Id	     Node-State	Node-Http-Address	Number-of-Running-Containers
> 192.168.1.69:57560	 DECOMMISSIONED	192.168.1.69:8042	                           0
> {noformat}
> And a full report like this:
> {noformat}
> >> bin/yarn node -status 192.168.1.69:57560
> 2016-11-04 08:55:08,928 INFO client.RMProxy: Connecting to ResourceManager at 0.0.0.0/0.0.0.0:8032
> Node Report :
> 	Node-Id : 192.168.1.69:57560
> 	Rack : /default-rack
> 	Node-State : DECOMMISSIONED
> 	Node-Http-Address : 192.168.1.69:8042
> 	Last-Health-Update : Fri 04/Nov/16 08:53:58:802PDT
> 	Health-Report :
> 	Containers : 0
> 	Memory-Used : 0MB
> 	Memory-Capacity : 8192MB
> 	CPU-Used : 0 vcores
> 	CPU-Capacity : 8 vcores
> 	Node-Labels :
> 	Resource Utilization by Node :
> 	Resource Utilization by Containers : PMem:0 MB, VMem:0 MB, VCores:0.0
> {noformat}
> If you then restart the ResourceManager, you get this report:
> {noformat}
> >> bin/yarn node -list -all
> 2016-11-04 08:57:18,512 INFO client.RMProxy: Connecting to ResourceManager at 0.0.0.0/0.0.0.0:8032
> Total Nodes:4
>          Node-Id	     Node-State	Node-Http-Address	Number-of-Running-Containers
>  192.168.1.69:-1	 DECOMMISSIONED	  192.168.1.69:-1	                           0
> {noformat}
> And when you try to get the full report on the now "-1" node, you get an NPE:
> {noformat}
> >> bin/yarn node -status 192.168.1.69:-1
> 2016-11-04 08:57:57,385 INFO client.RMProxy: Connecting to ResourceManager at 0.0.0.0/0.0.0.0:8032
> Exception in thread "main" java.lang.NullPointerException
> 	at org.apache.hadoop.yarn.client.cli.NodeCLI.printNodeStatus(NodeCLI.java:296)
> 	at org.apache.hadoop.yarn.client.cli.NodeCLI.run(NodeCLI.java:116)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> 	at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
> 	at org.apache.hadoop.yarn.client.cli.NodeCLI.main(NodeCLI.java:63)
> {noformat}


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org