[jira] [Commented] (TEZ-3072) Node blacklisting always reruns completed non-leaf tasks
[ https://issues.apache.org/jira/browse/TEZ-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115814#comment-15115814 ] Jason Lowe commented on TEZ-3072: - We also have issues with temporary fetch failure issues with a node causing all completed tasks from that node to re-run. In many ways the blacklisting logic is causing more problems than it is solving, at least with respect to fetch-failure related processing. It would be nice if we could configure blacklisting to ignore node effects involving shuffle (e.g.; fetch failures are not reported to the blacklisting logic, and blacklisted nodes don't cause compelted tasks to re-run). > Node blacklisting always reruns completed non-leaf tasks > > > Key: TEZ-3072 > URL: https://issues.apache.org/jira/browse/TEZ-3072 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Jason Lowe > > Recently a user ran a job with many vertices, and there was a bug in the > user's code that caused a problem in one of the trailing vertices in the > task. On some nodes enough tasks failed that the AM thought it needed to > blacklist those nodes. That blacklisting then caused many completed vertices > to re-run because it thought it needed to re-execute the non-leaf tasks that > had completed on those nodes. This wasted a lot of cluster resources and job > time for no benefit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TEZ-3072) Node blacklisting always reruns completed non-leaf tasks
[ https://issues.apache.org/jira/browse/TEZ-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115814#comment-15115814 ] Jason Lowe edited comment on TEZ-3072 at 1/25/16 7:30 PM: -- We also have issues with temporary fetch failure issues with a node causing all completed tasks from that node to re-run. In many ways the blacklisting logic is causing more problems than it is solving, at least with respect to fetch-failure related processing. It would be nice if we could configure blacklisting to ignore node effects involving shuffle (e.g.: fetch failures are not reported to the blacklisting logic, and blacklisted nodes don't cause completed tasks to re-run). was (Author: jlowe): We also have issues with temporary fetch failure issues with a node causing all completed tasks from that node to re-run. In many ways the blacklisting logic is causing more problems than it is solving, at least with respect to fetch-failure related processing. It would be nice if we could configure blacklisting to ignore node effects involving shuffle (e.g.; fetch failures are not reported to the blacklisting logic, and blacklisted nodes don't cause compelted tasks to re-run). > Node blacklisting always reruns completed non-leaf tasks > > > Key: TEZ-3072 > URL: https://issues.apache.org/jira/browse/TEZ-3072 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Jason Lowe > > Recently a user ran a job with many vertices, and there was a bug in the > user's code that caused a problem in one of the trailing vertices in the > task. On some nodes enough tasks failed that the AM thought it needed to > blacklist those nodes. That blacklisting then caused many completed vertices > to re-run because it thought it needed to re-execute the non-leaf tasks that > had completed on those nodes. This wasted a lot of cluster resources and job > time for no benefit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TEZ-3072) Node blacklisting always reruns completed non-leaf tasks
Jason Lowe created TEZ-3072: --- Summary: Node blacklisting always reruns completed non-leaf tasks Key: TEZ-3072 URL: https://issues.apache.org/jira/browse/TEZ-3072 Project: Apache Tez Issue Type: Bug Affects Versions: 0.7.0 Reporter: Jason Lowe Recently a user ran a job with many vertices, and there was a bug in the user's code that caused a problem in one of the trailing vertices in the task. On some nodes enough tasks failed that the AM thought it needed to blacklist those nodes. That blacklisting then caused many completed vertices to re-run because it thought it needed to re-execute the non-leaf tasks that had completed on those nodes. This wasted a lot of cluster resources and job time for no benefit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3072) Node blacklisting always reruns completed non-leaf tasks
[ https://issues.apache.org/jira/browse/TEZ-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15116156#comment-15116156 ] Bikas Saha commented on TEZ-3072: - A short term fix could be disabling the rerun of completed tasks (but continuing to blacklist the node to avoid scheduling more work there). A longer term effort towards putting machines in probation for a few cycles before giving up on them might help prevent cliffs like this, specially due to temporary glitches. > Node blacklisting always reruns completed non-leaf tasks > > > Key: TEZ-3072 > URL: https://issues.apache.org/jira/browse/TEZ-3072 > Project: Apache Tez > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Jason Lowe > > Recently a user ran a job with many vertices, and there was a bug in the > user's code that caused a problem in one of the trailing vertices in the > task. On some nodes enough tasks failed that the AM thought it needed to > blacklist those nodes. That blacklisting then caused many completed vertices > to re-run because it thought it needed to re-execute the non-leaf tasks that > had completed on those nodes. This wasted a lot of cluster resources and job > time for no benefit. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3071) run tez task on local mode is success,but run on cluster occurred this problem,java.lang.NullPointerException at com.teradata.sddg.sgprocessor.TezDataGeneratorTes
[ https://issues.apache.org/jira/browse/TEZ-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114993#comment-15114993 ] Lvpenglin commented on TEZ-3071: only mail to this address(u...@tez.apache.org) is ok? > run tez task on local mode is success,but run on cluster occurred this > problem,java.lang.NullPointerException at > com.teradata.sddg.sgprocessor.TezDataGeneratorTest$DataGenerationProcessor.run(TezDataGeneratorTest.java:78) > - > > Key: TEZ-3071 > URL: https://issues.apache.org/jira/browse/TEZ-3071 > Project: Apache Tez > Issue Type: Task > Environment: hadoop2.6.0+tez0.7.0 >Reporter: Lvpenglin > > 16/01/24 21:29:13 INFO client.DAGClientImpl: Waiting for DAG to start running > 16/01/24 21:29:25 INFO client.DAGClientImpl: DAG initialized: > CurrentState=Running > 16/01/24 21:29:26 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:42 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:47 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:52 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:57 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:30:02 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 3 > 16/01/24 21:30:02 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 >
[jira] [Commented] (TEZ-3071) run tez task on local mode is success,but run on cluster occurred this problem,java.lang.NullPointerException at com.teradata.sddg.sgprocessor.TezDataGeneratorTes
[ https://issues.apache.org/jira/browse/TEZ-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15114947#comment-15114947 ] Jeff Zhang commented on TEZ-3071: - Most likely sddg is null. And you'd better to ask this kind of question in tez user mail list. (u...@tez.apache.org) > run tez task on local mode is success,but run on cluster occurred this > problem,java.lang.NullPointerException at > com.teradata.sddg.sgprocessor.TezDataGeneratorTest$DataGenerationProcessor.run(TezDataGeneratorTest.java:78) > - > > Key: TEZ-3071 > URL: https://issues.apache.org/jira/browse/TEZ-3071 > Project: Apache Tez > Issue Type: Task > Environment: hadoop2.6.0+tez0.7.0 >Reporter: Lvpenglin > > 16/01/24 21:29:13 INFO client.DAGClientImpl: Waiting for DAG to start running > 16/01/24 21:29:25 INFO client.DAGClientImpl: DAG initialized: > CurrentState=Running > 16/01/24 21:29:26 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:42 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:47 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:52 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:57 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:30:02 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 3 > 16/01/24 21:30:02 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE
[jira] [Commented] (TEZ-3071) run tez task on local mode is success,but run on cluster occurred this problem,java.lang.NullPointerException at com.teradata.sddg.sgprocessor.TezDataGeneratorTes
[ https://issues.apache.org/jira/browse/TEZ-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115001#comment-15115001 ] Lvpenglin commented on TEZ-3071: Can I config some information in the eclipse run the code on the cluster mode?I want to debug the code like run on the cluster,is ok? > run tez task on local mode is success,but run on cluster occurred this > problem,java.lang.NullPointerException at > com.teradata.sddg.sgprocessor.TezDataGeneratorTest$DataGenerationProcessor.run(TezDataGeneratorTest.java:78) > - > > Key: TEZ-3071 > URL: https://issues.apache.org/jira/browse/TEZ-3071 > Project: Apache Tez > Issue Type: Task > Environment: hadoop2.6.0+tez0.7.0 >Reporter: Lvpenglin > > 16/01/24 21:29:13 INFO client.DAGClientImpl: Waiting for DAG to start running > 16/01/24 21:29:25 INFO client.DAGClientImpl: DAG initialized: > CurrentState=Running > 16/01/24 21:29:26 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:42 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:47 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:52 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:57 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:30:02 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 3 > 16/01/24 21:30:02 INFO client.DAGClientImpl:VertexStatus: VertexName:
[jira] [Commented] (TEZ-3071) run tez task on local mode is success,but run on cluster occurred this problem,java.lang.NullPointerException at com.teradata.sddg.sgprocessor.TezDataGeneratorTes
[ https://issues.apache.org/jira/browse/TEZ-3071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115037#comment-15115037 ] Jeff Zhang commented on TEZ-3071: - Yes, user mail list is for discussing user problems, after we confirm it is a bug, you can create jira ticket here. > run tez task on local mode is success,but run on cluster occurred this > problem,java.lang.NullPointerException at > com.teradata.sddg.sgprocessor.TezDataGeneratorTest$DataGenerationProcessor.run(TezDataGeneratorTest.java:78) > - > > Key: TEZ-3071 > URL: https://issues.apache.org/jira/browse/TEZ-3071 > Project: Apache Tez > Issue Type: Task > Environment: hadoop2.6.0+tez0.7.0 >Reporter: Lvpenglin > > 16/01/24 21:29:13 INFO client.DAGClientImpl: Waiting for DAG to start running > 16/01/24 21:29:25 INFO client.DAGClientImpl: DAG initialized: > CurrentState=Running > 16/01/24 21:29:26 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:26 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 0 Failed: 0 Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: 0 > Killed: 0 > 16/01/24 21:29:32 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 > 16/01/24 21:29:37 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:42 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:42 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:47 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 1 > 16/01/24 21:29:47 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:52 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:52 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:29:57 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 1 Failed: 0 > Killed: 0 FailedTaskAttempts: 2 > 16/01/24 21:29:57 INFO client.DAGClientImpl:VertexStatus: VertexName: > SALES_TRANSACTION Progress: 0% TotalTasks: 1 Succeeded: 0 Running: 0 Failed: > 0 Killed: 0 > 16/01/24 21:30:02 INFO client.DAGClientImpl: DAG: State: RUNNING Progress: 0% > TotalTasks: 2 Succeeded: 0 Running: 1 Failed: 0 Killed: 0 FailedTaskAttempts: > 3 > 16/01/24 21:30:02 INFO client.DAGClientImpl:VertexStatus: VertexName: > ASSOCIATE
