[jira] [Commented] (TEZ-1620) Wait for application finish before stopping MiniTezCluster

[ https://issues.apache.org/jira/browse/TEZ-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152727#comment-14152727 ] Jeff Zhang commented on TEZ-1620: - Attach the new patch. bq. How much the test runtime incr

[jira] [Commented] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152746#comment-14152746 ] Jeff Zhang commented on TEZ-1631: - Looks like we have same issue in master. Will check that

[jira] [Comment Edited] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152746#comment-14152746 ] Jeff Zhang edited comment on TEZ-1631 at 9/30/14 2:49 AM: -- Looks li

[jira] [Commented] (TEZ-1621) Should report error to AM before shuting down TezChild

[ https://issues.apache.org/jira/browse/TEZ-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152757#comment-14152757 ] Jeff Zhang commented on TEZ-1621: - bq. The new throw TezException is to shutdown the local r

[jira] [Comment Edited] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152746#comment-14152746 ] Jeff Zhang edited comment on TEZ-1631 at 9/30/14 3:25 AM: -- Will ver

[jira] [Commented] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152759#comment-14152759 ] Jeff Zhang commented on TEZ-1631: - Verify that no issue for master branch. We have resolved

[jira] [Updated] (TEZ-1633) TestTaskRecovery.testRecovery_OneTA - expected:<1> but was:<2>

[ https://issues.apache.org/jira/browse/TEZ-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1633: Attachment: Tez-1633-2.patch > TestTaskRecovery.testRecovery_OneTA - expected:<1> but was:<2> > --

[jira] [Commented] (TEZ-1633) TestTaskRecovery.testRecovery_OneTA - expected:<1> but was:<2>

[ https://issues.apache.org/jira/browse/TEZ-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152880#comment-14152880 ] Jeff Zhang commented on TEZ-1633: - [~apivovarov] Thanks for your finding and patch. I attac

[jira] [Commented] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152996#comment-14152996 ] Jeff Zhang commented on TEZ-1631: - Simulate the case in single node cluster ( using UnionExa

[jira] [Comment Edited] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152996#comment-14152996 ] Jeff Zhang edited comment on TEZ-1631 at 9/30/14 9:16 AM: -- Simulate

[jira] [Commented] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14153011#comment-14153011 ] Jeff Zhang commented on TEZ-1631: - One thing need to be careful is that in the high level co

[jira] [Updated] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1631: Attachment: Tez-1631-2.patch Attach a new patch with unit test. > Session dag submission timeout can result i

[jira] [Updated] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1631: Attachment: Tez-1631-3.patch Attach a new patch with minor change. > Session dag submission timeout can resul

[jira] [Updated] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1631: Attachment: Tez-1631-4.patch > Session dag submission timeout can result in duplicate DAG submissions > --

[jira] [Commented] (TEZ-1631) Session dag submission timeout can result in duplicate DAG submissions

[ https://issues.apache.org/jira/browse/TEZ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154058#comment-14154058 ] Jeff Zhang commented on TEZ-1631: - bq. This patch looks similar to TEZ-1433-v1.patch on TEZ-

[jira] [Created] (TEZ-1636) Duplicated code for checking exception types in TezTaskRunner and TaskRunnerCallable,

Jeff Zhang created TEZ-1636: --- Summary: Duplicated code for checking exception types in TezTaskRunner and TaskRunnerCallable, Key: TEZ-1636 URL: https://issues.apache.org/jira/browse/TEZ-1636 Project: Apache

[jira] [Commented] (TEZ-1621) Should report error to AM before shuting down TezChild

[ https://issues.apache.org/jira/browse/TEZ-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14154063#comment-14154063 ] Jeff Zhang commented on TEZ-1621: - bq. Please open a jira to track that. Open [TEZ-1636|http

[jira] [Updated] (TEZ-1470) TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1470: Summary: TaskAttemptFinishedEvent is recorded multiple times for the same task (was: TaskFinishedEvent is rec

[jira] [Created] (TEZ-1642) TestAMRecovery sometimes fail

Jeff Zhang created TEZ-1642: --- Summary: TestAMRecovery sometimes fail Key: TEZ-1642 URL: https://issues.apache.org/jira/browse/TEZ-1642 Project: Apache Tez Issue Type: Bug Reporter: Jeff

[jira] [Updated] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1470: Summary: Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task (was: Tas

[jira] [Updated] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1470: Description: TaskAttempt can move from SUCCEEDED to KILLED due to node failure. In this case TaskAttemptFinis

[jira] [Updated] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1470: Attachment: Tez-1470.patch > Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for > t

[jira] [Created] (TEZ-1644) Issues caused by multiple TaskAttemptFinishedEvent, TaskFinishedEvent, VertexFinishedEvent

Jeff Zhang created TEZ-1644: --- Summary: Issues caused by multiple TaskAttemptFinishedEvent, TaskFinishedEvent, VertexFinishedEvent Key: TEZ-1644 URL: https://issues.apache.org/jira/browse/TEZ-1644 Project: A

[jira] [Updated] (TEZ-1644) Issue due to Vertex/Task/TaskAttempt can finish multiple times

[ https://issues.apache.org/jira/browse/TEZ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1644: Summary: Issue due to Vertex/Task/TaskAttempt can finish multiple times (was: Issue due to TaskAttempt/Tasker

[jira] [Updated] (TEZ-1644) Issue due to TaskAttempt/Taskertex/Vertex can finish multiple times

[ https://issues.apache.org/jira/browse/TEZ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1644: Summary: Issue due to TaskAttempt/Taskertex/Vertex can finish multiple times (was: Issues caused by multiple

[jira] [Updated] (TEZ-1644) Issue due to TaskAttempt/Taskertex/Vertex can finish multiple times

[ https://issues.apache.org/jira/browse/TEZ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1644: Description: T > Issue due to TaskAttempt/Taskertex/Vertex can finish multiple times > ---

[jira] [Updated] (TEZ-1644) Issue due to Vertex/Task/TaskAttempt can finish multiple times

[ https://issues.apache.org/jira/browse/TEZ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1644: Description: Vertex/Task/TaskAttempt can move from SUCCEEDED to FAILED/KILLED, that means it would finish mul

[jira] [Commented] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163249#comment-14163249 ] Jeff Zhang commented on TEZ-1470: - Attach the patch. * use one Map to track whether TaskAtt

[jira] [Commented] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164416#comment-14164416 ] Jeff Zhang commented on TEZ-1647: - Looks like we should use List instead of Map for cachedIn

[jira] [Updated] (TEZ-1019) Re-factor routing of events to use common code path for normal and recovery flow.

[ https://issues.apache.org/jira/browse/TEZ-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1019: Attachment: Tez-1019.patch > Re-factor routing of events to use common code path for normal and recovery > fl

[jira] [Commented] (TEZ-1019) Re-factor routing of events to use common code path for normal and recovery flow.

[ https://issues.apache.org/jira/browse/TEZ-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164442#comment-14164442 ] Jeff Zhang commented on TEZ-1019: - [~bikassaha], attach one simple patch only to use the com

[jira] [Commented] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164533#comment-14164533 ] Jeff Zhang commented on TEZ-1647: - [~hitesh] bq. it calls context.addEvents(i1) and contex

[jira] [Commented] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164543#comment-14164543 ] Jeff Zhang commented on TEZ-1647: - Looking at [TEZ-1635|https://issues.apache.org/jira/brows

[jira] [Updated] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1647: Attachment: Tez-1647.patch > Issue with caching of events in VertexManager::onRootVertexInitialized > ---

[jira] [Commented] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165152#comment-14165152 ] Jeff Zhang commented on TEZ-1647: - Check the CustomPartitionVertex, it indeed have the case

[jira] [Updated] (TEZ-1644) Issue due to Vertex/Task/TaskAttempt can finish multiple times

[ https://issues.apache.org/jira/browse/TEZ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1644: Description: Vertex/Task/TaskAttempt can move from SUCCEEDED to FAILED/KILLED, that means it would finish mul

[jira] [Updated] (TEZ-1644) Issue due to Vertex/Task/TaskAttempt can finish multiple times

[ https://issues.apache.org/jira/browse/TEZ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1644: Description: Vertex/Task/TaskAttempt can move from SUCCEEDED to FAILED/KILLED, that means it would finish mul

[jira] [Commented] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166432#comment-14166432 ] Jeff Zhang commented on TEZ-1470: - [~hitesh] Use map looks clean to me, I saw some ugly code

[jira] [Updated] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1647: Attachment: Tez-1647-3.patch > Issue with caching of events in VertexManager::onRootVertexInitialized > -

[jira] [Commented] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166632#comment-14166632 ] Jeff Zhang commented on TEZ-1647: - [~hitesh] Attach new patch * using BlockingQueue instead

[jira] [Commented] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167945#comment-14167945 ] Jeff Zhang commented on TEZ-1647: - [~hitesh], Previously thought the addAll is not thread sa

[jira] [Updated] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

[ https://issues.apache.org/jira/browse/TEZ-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1647: Attachment: Tez-1647-4.patch > Issue with caching of events in VertexManager::onRootVertexInitialized > -

[jira] [Updated] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1470: Attachment: Tez-1470-2.patch > Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for >

[jira] [Commented] (TEZ-1470) Recovery fail due to TaskAttemptFinishedEvent is recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14167974#comment-14167974 ] Jeff Zhang commented on TEZ-1470: - [~hitesh] Attach new patch bq. can taskAttemptStatus map

[jira] [Commented] (TEZ-1470) Recovery fails due to TaskAttemptFinishedEvent being recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168990#comment-14168990 ] Jeff Zhang commented on TEZ-1470: - [~bikassaha] Thanks for your careful review. Yes, this do

[jira] [Comment Edited] (TEZ-1655) taskattemptstarted event is not adding nodeid/containerid to related entities in timelineserver

[ https://issues.apache.org/jira/browse/TEZ-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169032#comment-14169032 ] Jeff Zhang edited comment on TEZ-1655 at 10/13/14 7:29 AM: --- [~pram

[jira] [Commented] (TEZ-1655) taskattemptstarted event is not adding nodeid/containerid to related entities in timelineserver

[ https://issues.apache.org/jira/browse/TEZ-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169032#comment-14169032 ] Jeff Zhang commented on TEZ-1655: - [~pramachandran] the relationships are stored in the othe

[jira] [Commented] (TEZ-1629) ContainerLauncherImpl's event handler thread should check for threadpool's status before submitting a task

[ https://issues.apache.org/jira/browse/TEZ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169096#comment-14169096 ] Jeff Zhang commented on TEZ-1629: - [~rajesh.balamohan] This issue happens when AM is shuttin

[jira] [Updated] (TEZ-1629) ContainerLauncherImpl's event handler thread should check for threadpool's status before submitting a task

[ https://issues.apache.org/jira/browse/TEZ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1629: Attachment: Tez-1629.patch > ContainerLauncherImpl's event handler thread should check for threadpool's > sta

[jira] [Comment Edited] (TEZ-1629) ContainerLauncherImpl's event handler thread should check for threadpool's status before submitting a task

[ https://issues.apache.org/jira/browse/TEZ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169096#comment-14169096 ] Jeff Zhang edited comment on TEZ-1629 at 10/13/14 9:02 AM: --- [~raje

[jira] [Created] (TEZ-1657) Consolite recovery logs to XXXRecoveryData for DAG/Vertex/Task/TaskAttempt

Jeff Zhang created TEZ-1657: --- Summary: Consolite recovery logs to XXXRecoveryData for DAG/Vertex/Task/TaskAttempt Key: TEZ-1657 URL: https://issues.apache.org/jira/browse/TEZ-1657 Project: Apache Tez

[jira] [Created] (TEZ-1660) successfulAttempt is not set correctly when recovery in the case of speculation

Jeff Zhang created TEZ-1660: --- Summary: successfulAttempt is not set correctly when recovery in the case of speculation Key: TEZ-1660 URL: https://issues.apache.org/jira/browse/TEZ-1660 Project: Apache Tez

[jira] [Commented] (TEZ-1470) Recovery fails due to TaskAttemptFinishedEvent being recorded multiple times for the same task

[ https://issues.apache.org/jira/browse/TEZ-1470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170198#comment-14170198 ] Jeff Zhang commented on TEZ-1470: - Create [TEZ-1660|https://issues.apache.org/jira/browse/TE

[jira] [Commented] (TEZ-1323) Insufficent diagnostics on console when dag fails due to an exception in a task

[ https://issues.apache.org/jira/browse/TEZ-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170896#comment-14170896 ] Jeff Zhang commented on TEZ-1323: - It is resolved in -[TEZ-1238|https://issues.apache.org/ji

[jira] [Commented] (TEZ-1666) UserPayload should be null if the payload is not specified

[ https://issues.apache.org/jira/browse/TEZ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171740#comment-14171740 ] Jeff Zhang commented on TEZ-1666: - It looks like Context.getUserPayload won't be null, found

[jira] [Commented] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173768#comment-14173768 ] Jeff Zhang commented on TEZ-1584: - [~hitesh], I manually test it on TestOrderedWordCount. Cl

[jira] [Updated] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1584: Attachment: Tez-1584-2.patch > Restore counters from DAGFinishedEvent when DAG is completed >

[jira] [Updated] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1584: Description: Follow up [TEZ-853|https://issues.apache.org/jira/browse/TEZ-853], when DAG is completed, the re

[jira] [Commented] (TEZ-1629) ContainerLauncherImpl's event handler thread should check for threadpool's status before submitting a task

[ https://issues.apache.org/jira/browse/TEZ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173789#comment-14173789 ] Jeff Zhang commented on TEZ-1629: - bq. May be we could log the status of the threadpool exec

[jira] [Commented] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174454#comment-14174454 ] Jeff Zhang commented on TEZ-1267: - [~sseth] Could you help review it ? > Exception handling

[jira] [Created] (TEZ-1677) Add Jeff Zhang to team list

Jeff Zhang created TEZ-1677: --- Summary: Add Jeff Zhang to team list Key: TEZ-1677 URL: https://issues.apache.org/jira/browse/TEZ-1677 Project: Apache Tez Issue Type: Bug Reporter: Jeff Z

[jira] [Updated] (TEZ-1677) Add Jeff Zhang to team list

[ https://issues.apache.org/jira/browse/TEZ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1677: Attachment: Tez-1677.patch > Add Jeff Zhang to team list > --- > > Key

[jira] [Resolved] (TEZ-1677) Add Jeff Zhang to team list

[ https://issues.apache.org/jira/browse/TEZ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved TEZ-1677. - Resolution: Fixed > Add Jeff Zhang to team list > --- > > Key: TEZ-1

[jira] [Commented] (TEZ-1677) Add Jeff Zhang to team list

[ https://issues.apache.org/jira/browse/TEZ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174643#comment-14174643 ] Jeff Zhang commented on TEZ-1677: - Committed to master. > Add Jeff Zhang to team list > ---

[jira] [Commented] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174939#comment-14174939 ] Jeff Zhang commented on TEZ-1584: - Committed to master > Restore counters from DAGFinished

[jira] [Closed] (TEZ-1677) Add Jeff Zhang to team list

[ https://issues.apache.org/jira/browse/TEZ-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang closed TEZ-1677. --- > Add Jeff Zhang to team list > --- > > Key: TEZ-1677 > URL:

[jira] [Closed] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang closed TEZ-1584. --- > Restore counters from DAGFinishedEvent when DAG is completed > ---

[jira] [Comment Edited] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175134#comment-14175134 ] Jeff Zhang edited comment on TEZ-1584 at 10/17/14 3:16 PM: --- [~hite

[jira] [Commented] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175134#comment-14175134 ] Jeff Zhang commented on TEZ-1584: - [~hitesh] Looks like can not open it once closed, I will

[jira] [Commented] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176536#comment-14176536 ] Jeff Zhang commented on TEZ-1584: - [~hitesh] I have update the CHANGES.txt and cherry-pick

[jira] [Commented] (TEZ-1584) Restore counters from DAGFinishedEvent when DAG is completed

[ https://issues.apache.org/jira/browse/TEZ-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176545#comment-14176545 ] Jeff Zhang commented on TEZ-1584: - Sorry, forget the "-x" when cherry-pick :( > Restore cou

[jira] [Created] (TEZ-1685) Remove YARNMaster which is never used

Jeff Zhang created TEZ-1685: --- Summary: Remove YARNMaster which is never used Key: TEZ-1685 URL: https://issues.apache.org/jira/browse/TEZ-1685 Project: Apache Tez Issue Type: Bug Report

[jira] [Updated] (TEZ-1685) Remove YARNMaster which is never used

[ https://issues.apache.org/jira/browse/TEZ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1685: Priority: Minor (was: Major) > Remove YARNMaster which is never used > -

[jira] [Updated] (TEZ-1685) Remove YARNMaster which is never used

[ https://issues.apache.org/jira/browse/TEZ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1685: Attachment: TEZ-1685.patch Attach the patch. > Remove YARNMaster which is never used > --

[jira] [Created] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

Jeff Zhang created TEZ-1686: --- Summary: TestRecoveryParser.testGetLastCompletedDAG fails sometimes Key: TEZ-1686 URL: https://issues.apache.org/jira/browse/TEZ-1686 Project: Apache Tez Issue Type: B

[jira] [Updated] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

[ https://issues.apache.org/jira/browse/TEZ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1686: Attachment: TEZ-1686.patch [~hitesh] Please help review it. > TestRecoveryParser.testGetLastCompletedDAG fai

[jira] [Updated] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

[ https://issues.apache.org/jira/browse/TEZ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1686: Description: The test would fail if the randon number generated is 0. > TestRecoveryParser.testGetLastComplete

[jira] [Updated] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

[ https://issues.apache.org/jira/browse/TEZ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1686: Description: The test would fail if the random number generated is 0. (was: The test would fail if the randon

[jira] [Assigned] (TEZ-1625) TestVertexImpl occasionally hangs

[ https://issues.apache.org/jira/browse/TEZ-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang reassigned TEZ-1625: --- Assignee: Jeff Zhang > TestVertexImpl occasionally hangs > - > >

[jira] [Updated] (TEZ-1625) TestVertexImpl occasionally hangs

[ https://issues.apache.org/jira/browse/TEZ-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1625: Attachment: TEZ-1625.patch > TestVertexImpl occasionally hangs > - > >

[jira] [Commented] (TEZ-1625) TestVertexImpl occasionally hangs

[ https://issues.apache.org/jira/browse/TEZ-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176622#comment-14176622 ] Jeff Zhang commented on TEZ-1625: - The root cause is that DrainDispatcher may been created 2

[jira] [Resolved] (TEZ-1586) Vertex should always been recovered to FAIL when there's commit in progress

[ https://issues.apache.org/jira/browse/TEZ-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang resolved TEZ-1586. - Resolution: Invalid It is invalid, when DAG is in commit that means its vertices are all succeeded > Vertex

[jira] [Created] (TEZ-1687) Use logIdentifier in VertexImpl when logging

Jeff Zhang created TEZ-1687: --- Summary: Use logIdentifier in VertexImpl when logging Key: TEZ-1687 URL: https://issues.apache.org/jira/browse/TEZ-1687 Project: Apache Tez Issue Type: Bug

[jira] [Updated] (TEZ-1687) Use logIdentifier of Vertex for logging

[ https://issues.apache.org/jira/browse/TEZ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1687: Summary: Use logIdentifier of Vertex for logging (was: Use logIdentifier in VertexImpl when logging) > Use l

[jira] [Updated] (TEZ-1586) Vertex should always been recovered to FAIL when DAG is committing

[ https://issues.apache.org/jira/browse/TEZ-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1586: Summary: Vertex should always been recovered to FAIL when DAG is committing (was: Vertex should always been r

[jira] [Commented] (TEZ-1586) Vertex should always been recovered to FAIL when DAG is committing

[ https://issues.apache.org/jira/browse/TEZ-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177646#comment-14177646 ] Jeff Zhang commented on TEZ-1586: - [~hitesh], [~bikassaha], Sorry for didn't make it clear,

[jira] [Commented] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

[ https://issues.apache.org/jira/browse/TEZ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177676#comment-14177676 ] Jeff Zhang commented on TEZ-1686: - [~hitesh] thanks for your review. And jiras like this abo

[jira] [Created] (TEZ-1689) Exception handling for EdgeManagePlugin and InputInitializer

Jeff Zhang created TEZ-1689: --- Summary: Exception handling for EdgeManagePlugin and InputInitializer Key: TEZ-1689 URL: https://issues.apache.org/jira/browse/TEZ-1689 Project: Apache Tez Issue Type

[jira] [Created] (TEZ-1691) Check whether VertexManager is null before handling VertexManageEvent

Jeff Zhang created TEZ-1691: --- Summary: Check whether VertexManager is null before handling VertexManageEvent Key: TEZ-1691 URL: https://issues.apache.org/jira/browse/TEZ-1691 Project: Apache Tez I

[jira] [Commented] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177986#comment-14177986 ] Jeff Zhang commented on TEZ-1267: - bq. ROUTE_EVENT_TRANSITIONS from the NEW / INITIALIZING /

[jira] [Commented] (TEZ-1525) BroadcastLoadGen testcase

[ https://issues.apache.org/jira/browse/TEZ-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178060#comment-14178060 ] Jeff Zhang commented on TEZ-1525: - [~gopalv] Looks like you didn't commit it to branch-0.5

[jira] [Commented] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

[ https://issues.apache.org/jira/browse/TEZ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178083#comment-14178083 ] Jeff Zhang commented on TEZ-1686: - Committed to both master and branch-0.5 > TestRecoveryPa

[jira] [Updated] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1267: Attachment: TEZ-1267-2.patch [~sseth] Attach the new patch, please help review it. > Exception handling when

[jira] [Commented] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179453#comment-14179453 ] Jeff Zhang commented on TEZ-1267: - [~sseth] I found another issue, will update the patch soo

[jira] [Updated] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1267: Attachment: TEZ-1267-3.patch > Exception handling when Routing Events > --

[jira] [Commented] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179544#comment-14179544 ] Jeff Zhang commented on TEZ-1267: - [~sseth] Attach the new patch. The issue I mention is th

[jira] [Updated] (TEZ-1629) Replace ThreadPool's default RejectedExecutionHandler in ContainerLauncherImpl to void abort when AM shutdown

[ https://issues.apache.org/jira/browse/TEZ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1629: Summary: Replace ThreadPool's default RejectedExecutionHandler in ContainerLauncherImpl to void abort when AM

[jira] [Commented] (TEZ-1629) Replace ThreadPool's default RejectedExecutionHandler in ContainerLauncherImpl to void abort when AM shutdown

[ https://issues.apache.org/jira/browse/TEZ-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179605#comment-14179605 ] Jeff Zhang commented on TEZ-1629: - Committed to both master and branch-0.5 > Replace Thread

[jira] [Updated] (TEZ-1686) TestRecoveryParser.testGetLastCompletedDAG fails sometimes

[ https://issues.apache.org/jira/browse/TEZ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1686: Fix Version/s: 0.5.2 > TestRecoveryParser.testGetLastCompletedDAG fails sometimes > --

[jira] [Updated] (TEZ-1267) Exception handling when Routing Events

[ https://issues.apache.org/jira/browse/TEZ-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-1267: Attachment: TEZ-1267-4.patch > Exception handling when Routing Events > --

<    14   15   16   17   18   19   20   21   22   23   >