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

Jeff Zhang commented on TEZ-2437:
---------------------------------

[~pramachandran] [~tiwari] I think the simple solution is don't set 
DAGAppMaster as null so that we can still get the ApplicationReport in local 
mode after AM is shutdown just like we can get the ApplicationReport in 
non-local mode. This can make the local/non-local model's behavior consistent 
as [~hitesh] [~bikassaha] mentioned. 

{code}
    if (dagAppMaster != null) {
      dagAppMaster.stop();
     dagAppMaster = null;   // remove this line
    }
{code}
 

> FilterLinesByWord NPEs when run in Localmode
> --------------------------------------------
>
>                 Key: TEZ-2437
>                 URL: https://issues.apache.org/jira/browse/TEZ-2437
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>         Environment: Tez Localmode only
>            Reporter: Amit Tiwari
>         Attachments: TEZ-2437.patch, TEZ-2437.patch
>
>
> Subsequent to Tez-1969 [https://issues.apache.org/jira/browse/TEZ-1969] I've 
> noticed that org.apache.tez.mapreduce.examples.FilterLinesByWord.java NPEs 
> with this stack trace, when run on Localmode:
> at 
> org.apache.tez.client.LocalClient.getApplicationReport(LocalClient.java:145)
>       at 
> org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getAppReport(DAGClientRPCImpl.java:213)
>       at 
> org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.createAMProxyIfNeeded(DAGClientRPCImpl.java:230)
>       at 
> org.apache.tez.dag.api.client.rpc.DAGClientRPCImpl.getVertexStatus(DAGClientRPCImpl.java:102)
>       at 
> org.apache.tez.dag.api.client.DAGClientImpl.getVertexStatusViaAM(DAGClientImpl.java:257)
>       at 
> org.apache.tez.dag.api.client.DAGClientImpl.getVertexStatus(DAGClientImpl.java:166)
>       at 
> org.apache.tez.mapreduce.examples.ExampleDriver.printDAGStatus(ExampleDriver.java:122)



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

Reply via email to