Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
It would be possible that dag is not initialized when DAGClientHandler#getVertexStatus is invoked so that DAGClientHandler#getVertexStatus would throw exception.
2015-05-10 04:29:26,554 INFO [IPC Server handler 0 on 51881] ipc.Server: IPC Server handler 0 on 51881, call org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPB.getVertexStatus from 10.79.246.151:53112 Call#188 Retry#0^M org.apache.tez.dag.api.TezException: Unknown vertexName: initialmap^M at org.apache.tez.dag.api.client.DAGClientHandler.getVertexStatus(DAGClientHandler.java:75)^M at org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPBServerImpl.getVertexStatus(DAGClientAMProtocolBlockingPBServerImpl.java:121)^M at org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolRPC$DAGClientAMProtocol$2.callBlockingMethod(DAGClientAMProtocolRPC.java:7467)^M at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)^M at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)^M at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2049)^M at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2045)^M at java.security.AccessController.doPrivileged(Native Method)^M at javax.security.auth.Subject.doAs(Subject.java:415)^M at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)^M at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2043)^M
Attachments
Attachments
Issue Links
- is related to
-
TEZ-1961 Remove misleading exception "No running dag" from AM logs
- Closed