[jira] [Commented] (YARN-5837) NPE when getting node status of a decommissioned node after an RM restart
[
https://issues.apache.org/jira/browse/YARN-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15937617#comment-15937617
]
Yeliang Cang commented on YARN-5837:
Thanks!
> 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
> Fix For: 2.8.0, 2.7.4, 3.0.0-alpha2
>
> 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.15#6346)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5837) NPE when getting node status of a decommissioned node after an RM restart
[
https://issues.apache.org/jira/browse/YARN-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15638026#comment-15638026
]
Robert Kanter commented on YARN-5837:
-
Thanks for the quick review!
> 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
> Fix For: 2.8.0, 2.7.4, 3.0.0-alpha2
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5837) NPE when getting node status of a decommissioned node after an RM restart
[
https://issues.apache.org/jira/browse/YARN-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15637944#comment-15637944
]
Hudson commented on YARN-5837:
--
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10775 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10775/])
YARN-5837. NPE when getting node status of a decommissioned node after (jlowe:
rev 6bb741ff0ef208a8628bc64d6537999d4cd67955)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/NodesListManager.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNM.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMRestart.java
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5837) NPE when getting node status of a decommissioned node after an RM restart
[
https://issues.apache.org/jira/browse/YARN-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-5837) NPE when getting node status of a decommissioned node after an RM restart
[
https://issues.apache.org/jira/browse/YARN-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15637372#comment-15637372
]
Hadoop QA commented on YARN-5837:
-
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
26s{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
8s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
32s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
39s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
17s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
1s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 35m
27s{color} | {color:green} hadoop-yarn-server-resourcemanager in the patch
passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
18s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 51m 35s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:9560f25 |
| JIRA Issue | YARN-5837 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12837203/YARN-5837.001.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux aa912f2989b7 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12
17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / abfc15d |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/13789/testReport/ |
| modules | C:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
|
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/13789/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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
>
>
>
[jira] [Commented] (YARN-5837) NPE when getting node status of a decommissioned node after an RM restart
[
https://issues.apache.org/jira/browse/YARN-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15636844#comment-15636844
]
Robert Kanter commented on YARN-5837:
-
The problem is due to this code in the {{NodesListManager}}:
{code:java}
private void setDecomissionedNMs() {
Set excludeList = hostsReader.getExcludedHosts();
for (final String host : excludeList) {
NodeId nodeId = createUnknownNodeId(host);
RMNodeImpl rmNode = new RMNodeImpl(nodeId,
rmContext, host, -1, -1, new UnknownNode(host), null, null);
rmContext.getInactiveRMNodes().put(nodeId, rmNode);
rmNode.handle(new RMNodeEvent(nodeId, RMNodeEventType.DECOMMISSION));
}
}
{code}
We set the {{Resource}} capability of the node to {{null}}. After the RM
restart, we no longer know the resource capabilities of the node because it's
down now, but having 0 resources is more reasonable than {{null}}, and should
fix the CLI and API.
> 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
>
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
