kyungwan nam created YARN-8269:
----------------------------------

             Summary: NPE happens when submit distributed shell with 
non-existing queue
                 Key: YARN-8269
                 URL: https://issues.apache.org/jira/browse/YARN-8269
             Project: Hadoop YARN
          Issue Type: Bug
          Components: distributed-shell
            Reporter: kyungwan nam


when submit the distributed shell with non-existing queue, NullPointerException 
happens as follows.
{code:java}
18/05/04 12:20:20 INFO distributedshell.Client: Initializing Client
18/05/04 12:20:20 INFO distributedshell.Client: Running Client
18/05/04 12:20:20 INFO client.AHSProxy: Connecting to Application History 
server at node1/10.1.1.1:10200
18/05/04 12:20:21 INFO distributedshell.Client: Got Cluster metric info from 
ASM, numNodeManagers=1
18/05/04 12:20:21 INFO distributedshell.Client: Got Cluster node info from ASM
18/05/04 12:20:21 INFO distributedshell.Client: Got node report from ASM for, 
nodeId=node2:45454, nodeAddressnode2:8042, nodeRackName/rack-9, 
nodeNumContainers0
18/05/04 12:20:21 FATAL distributedshell.Client: Error running Client
java.lang.NullPointerException
        at 
org.apache.hadoop.yarn.applications.distributedshell.Client.run(Client.java:462)
        at 
org.apache.hadoop.yarn.applications.distributedshell.Client.main(Client.java:215)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
{code}
 
that makes it difficult to find the cause.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to