date:20150507

[jira] [Commented] (TEZ-1961) Remove misleading exception No running dag from AM logs

2015-05-07 Thread TezQA (JIRA)


[ 
https://issues.apache.org/jira/browse/TEZ-1961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14532138#comment-14532138
 ] 

TezQA commented on TEZ-1961:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12731085/TEZ-1961-3.patch
  against master revision 02870f0.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/649//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/649//console

This message is automatically generated.

 Remove misleading exception No running dag from AM logs
 -

 Key: TEZ-1961
 URL: https://issues.apache.org/jira/browse/TEZ-1961
 Project: Apache Tez
  Issue Type: Improvement
Reporter: Siddharth Seth
Assignee: Jeff Zhang
Priority: Critical
 Attachments: TEZ-1961-1.patch, TEZ-1961-2.patch, TEZ-1961-3.patch


 {code}
 15/01/14 16:45:06 INFO ipc.Server: IPC Server handler 0 on 51000, call 
 org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPB.getDAGStatus 
 from  Call#0 Retry#0
 org.apache.tez.dag.api.TezException: No running dag at present
   at 
 org.apache.tez.dag.api.client.DAGClientHandler.getDAG(DAGClientHandler.java:84)
   at 
 org.apache.tez.dag.api.client.DAGClientHandler.getACLManager(DAGClientHandler.java:151)
   at 
 org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPBServerImpl.getDAGStatus(DAGClientAMProtocolBlockingPBServerImpl.java:94)
   at 
 org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolRPC$DAGClientAMProtocol$2.callBlockingMethod(DAGClientAMProtocolRPC.java:7375)
   at 
 org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:617)
   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:962)
   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2041)
   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2037)
   at java.security.AccessController.doPrivileged(Native Method)
   at javax.security.auth.Subject.doAs(Subject.java:415)
   at 
 org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
   at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2035)
 15/01/14 16:45:06 INFO client.DAGClientImpl: DAG initialized: 
 CurrentState=Running
 {code}
 This exception shows up fairly often and isn't very relevant - queries before 
 a DAG is submitted to the AM.
 This is very misleading, especially for folks new to Tez, and should be 
 removed.



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

Success: TEZ-1961 PreCommit Build #649

2015-05-07 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/TEZ-1961
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/649/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2850 lines...]
[INFO] Final Memory: 70M/931M
[INFO] 




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12731085/TEZ-1961-3.patch
  against master revision 02870f0.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/649//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/649//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
2a8b86df1ccfb4cd7e51a1a513e609b74e98353f logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #646
Archived 44 artifacts
Archive block size is 32768
Received 2 blocks and 2706810 bytes
Compression is 2.4%
Took 1.1 sec
Description set: TEZ-1961
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Commented] (TEZ-2426) Task input not complete before sending Task completed event

2015-05-07 Thread Siddharth Seth (JIRA)

[
https://issues.apache.org/jira/browse/TEZ-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14533094#comment-14533094
]

Siddharth Seth commented on TEZ-2426:
-

[~bikassaha] - do you have additional logs - the entire AM log specifically.
There seems to be a discrepancy in the AM / task log times as well. Assuming
the nodes are out of sync.

I can see how the exception happens during execution of the next task - since
we don't join on the eventRouter thread.
However, I'm not sure how the FAILED message will go through for the previous
attempt as a result of this. It should have gone through for the currently
running task. If it went for the previous task - the AM should have thrown an
error related to an invalid taskAttemptId. That leads me to believe something
else is broken at the same time.

Task input not complete before sending Task completed event
---

Key: TEZ-2426
URL: https://issues.apache.org/jira/browse/TEZ-2426
Project: Apache Tez
Issue Type: Bug
Reporter: Bikas Saha
Priority: Critical
Attachments: am.log, container.log

Sequence of events
1) Task A starts in a container
2) Task A complete event comes to AM
3) Task B starts in the same container
4) Task A's input calls some method on its context. Crashes with NPE
5) The crash sends an input failed event for Task A to the AM
6) Task A state machine crashes saying cannot handle failed after success
In some cases, it could be that status update event is also sent after
completion, though not sure if its related to the failed event being sent.

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

[jira] [Commented] (TEZ-2426) Task input not complete before sending Task completed event

2015-05-07 Thread Siddharth Seth (JIRA)


[ 
https://issues.apache.org/jira/browse/TEZ-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14533096#comment-14533096
 ] 

Siddharth Seth commented on TEZ-2426:
-

The status update event after the task failed is also strange. Will look into 
that. The thread for the last running task may not be exiting properly.

 Task input not complete before sending Task completed event
 ---

 Key: TEZ-2426
 URL: https://issues.apache.org/jira/browse/TEZ-2426
 Project: Apache Tez
  Issue Type: Bug
Reporter: Bikas Saha
Priority: Critical
 Attachments: am.log, container.log


 Sequence of events
 1) Task A starts in a container
 2) Task A complete event comes to AM
 3) Task B starts in the same container
 4) Task A's input calls some method on its context. Crashes with NPE
 5) The crash sends an input failed event for Task A to the AM
 6) Task A state machine crashes saying cannot handle failed after success
 In some cases, it could be that status update event is also sent after 
 completion, though not sure if its related to the failed event being sent.



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

68 matches

Mail list logo