[
https://issues.apache.org/jira/browse/TEZ-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14145602#comment-14145602
]
Rajesh Balamohan commented on TEZ-1612:
---------------------------------------
agreed. But this issue happened because downstream vertex started before
upstream vertices changed its parallelism (which is fixed in master).
>>>>>>>
2014-09-22 19:20:29,477 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Creating 1 for vertex:
vertex_1411413615885_0001_1_00 [scope-105]
2014-09-22 19:20:29,503 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Creating 1 for vertex:
vertex_1411413615885_0001_1_01 [scope-99]
2014-09-22 19:20:29,529 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Creating 2 for vertex:
vertex_1411413615885_0001_1_02 [scope-106]
2014-09-22 19:20:29,541 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Creating 21 for vertex:
vertex_1411413615885_0001_1_03 [scope-107]
...
...
2014-09-22 19:20:29,767 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Source vertex started:
vertex_1411413615885_0001_1_01 for vertex: vertex_1411413615885_0001_1_03
numStartedSources: 1 numSources: 2
2014-09-22 19:20:29,767 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Cannot start vertex:
vertex_1411413615885_0001_1_03 [scope-107] numStartedSources: 1 numSources: 2
2014-09-22 19:20:29,768 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Source vertex started:
vertex_1411413615885_0001_1_01 for vertex: vertex_1411413615885_0001_1_02
numStartedSources: 1 numSources: 2
2014-09-22 19:20:29,768 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Cannot start vertex:
vertex_1411413615885_0001_1_02 [scope-106] numStartedSources: 1 numSources: 2
2014-09-22 19:20:29,768 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Source vertex started:
vertex_1411413615885_0001_1_00 for vertex: vertex_1411413615885_0001_1_02
numStartedSources: 2 numSources: 2
...
2014-09-22 19:20:29,790 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: vertex_1411413615885_0001_1_02
[scope-106] transitioned from INITED to RUNNING due to event V_START
2014-09-22 19:20:29,797 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Source vertex started:
vertex_1411413615885_0001_1_02 for vertex: vertex_1411413615885_0001_1_03
numStartedSources: 2 numSources: 2
...
2014-09-22 19:20:29,797 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: vertex_1411413615885_0001_1_03
[scope-107] transitioned from INITED to RUNNING due to event V_START
2014-09-22 19:20:35,387 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Vertex
vertex_1411413615885_0001_1_03 [scope-107] parallelism set to 1 from 21 <==
upstream vertex changing parallelism after scope-107 went to running state
2014-09-22 19:20:35,393 INFO [AsyncDispatcher event handler]
org.apache.tez.dag.app.dag.impl.VertexImpl: Vertex
vertex_1411413615885_0001_1_02 [scope-106] parallelism set to 1 from 2
>>>>>>>
> Pig on tez unit test intermittent hang
> --------------------------------------
>
> Key: TEZ-1612
> URL: https://issues.apache.org/jira/browse/TEZ-1612
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.0
> Reporter: Daniel Dai
> Assignee: Bikas Saha
> Attachments: DAG1.png, syslog_dag_1411413615885_0001_1,
> testfail1.log.tar.gz
>
>
> Several Pig unit tests hang intermittently. For example,
> TestNewPlanImplicitSplit.testImplicitSplitInCoGroup, which is a DAG of 4
> nodes:
> !DAG1.png!
> It uses auto-parallelism, vertex 106 change parallelism from 2->1, and vertex
> 107 from 21->1.
> Log attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
