[jira] [Updated] (TEZ-2304) InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery
[ https://issues.apache.org/jira/browse/TEZ-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2304: Labels: Recovery (was: ) InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery Key: TEZ-2304 URL: https://issues.apache.org/jira/browse/TEZ-2304 Project: Apache Tez Issue Type: Bug Affects Versions: 0.6.0 Reporter: Jason Lowe Labels: Recovery Attachments: 168563_recovery.gz I saw a Tez AM throw a few InvalidStateTransitonException (sic) instances during recovery complaining about TA_SCHEDULE arriving at the START_WAIT state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TEZ-2304) InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery
[
https://issues.apache.org/jira/browse/TEZ-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14557994#comment-14557994
]
Jeff Zhang edited comment on TEZ-2304 at 5/25/15 6:28 AM:
--
In this log, there's only recovery events for
attempt_1428329756093_168563_1_00_006728_1 (attempt_1) but no
attempt_1428329756093_168563_1_00_006728_0 (attempt_0)
It is possible that attempt_0 is killed before it started so there's no any
recovery events for it. But we should log the TaskAttemptFinishedEvent even
when there's no TaskAttemptStartedEvent. (link this with TEZ-2456)
Otherwise in this case, attempt_0 wouldn't be recovered and attempt_1 will be
recovered, and when a new attempt is scheduled its task attempt id would be the
same as the attempt_1, because we create task attempt id by using the
attempts.size();
{code}
TaskAttempt attempt = createAttempt(attempts.size());
{code}
That's why we would see the following weird transition ( from NEW to KILLED,
and then form NEW to START_WAIT), actually these are 2 different task attempt
but with the same attempt id, so their state machines are messed up together.
{noformat}
2015-04-09 20:05:42,055 INFO [AsyncDispatcher event handler]
impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt
Transitioned from NEW to KILLED due to event TA_RECOVER
{noformat}
{noformat}
2015-04-09 20:05:45,748 INFO [AsyncDispatcher event handler]
impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt
Transitioned from NEW to START_WAIT due to event TA_SCHEDULE
{noformat}
was (Author: zjffdu):
In this log, there's only recovery events for
attempt_1428329756093_168563_1_00_006728_1 (attempt_1) but no
attempt_1428329756093_168563_1_00_006728_0 (attempt_0)
It is possible that attempt_0 is killed before it started so there's no any
recovery events for it. We should log the TaskAttemptFinishedEvent even when
there's no TaskAttemptStartedEvent. (link this with TEZ-2456)
In this case, attempt_0 wouldn't be recovered and attempt_1 will be recovered,
and when a new attempt is scheduled its task attempt id would be the same as
the attempt_1, because we create task attempt id by using the attempts.size();
{code}
TaskAttempt attempt = createAttempt(attempts.size());
{code}
That's why we would see the following weird transition ( from NEW to KILLED,
and then form NEW to START_WAIT), actually these are 2 different task attempt
but with the same attempt id, so their state machines are messed up together.
{noformat}
2015-04-09 20:05:42,055 INFO [AsyncDispatcher event handler]
impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt
Transitioned from NEW to KILLED due to event TA_RECOVER
{noformat}
{noformat}
2015-04-09 20:05:45,748 INFO [AsyncDispatcher event handler]
impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt
Transitioned from NEW to START_WAIT due to event TA_SCHEDULE
{noformat}
InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery
Key: TEZ-2304
URL: https://issues.apache.org/jira/browse/TEZ-2304
Project: Apache Tez
Issue Type: Bug
Affects Versions: 0.6.0
Reporter: Jason Lowe
Attachments: 168563_recovery.gz
I saw a Tez AM throw a few InvalidStateTransitonException (sic) instances
during recovery complaining about TA_SCHEDULE arriving at the START_WAIT
state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-2311) AM can hang if kill received while recovering from previous attempt
[ https://issues.apache.org/jira/browse/TEZ-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2311: Labels: Recovery (was: ) AM can hang if kill received while recovering from previous attempt --- Key: TEZ-2311 URL: https://issues.apache.org/jira/browse/TEZ-2311 Project: Apache Tez Issue Type: Bug Affects Versions: 0.6.0 Reporter: Jason Lowe Labels: Recovery We saw an instance of a Tez job hanging despite receiving multiple kill requests from clients. The AM was recovering from a prior attempt when the first kill request arrived. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2322) Succeeded count wrong for Pig on Tez job, decreased 380 = 181
[
https://issues.apache.org/jira/browse/TEZ-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated TEZ-2322:
Labels: Recovery (was: )
Succeeded count wrong for Pig on Tez job, decreased 380 = 181
--
Key: TEZ-2322
URL: https://issues.apache.org/jira/browse/TEZ-2322
Project: Apache Tez
Issue Type: Bug
Affects Versions: 0.5.2
Environment: HDP 2.2
Reporter: Hari Sekhon
Priority: Minor
Labels: Recovery
Attachments: attempt1_syslog_dag_1427546104095_0146_1,
attempt2_syslog, attempt2_syslog_dag_1427546104095_0146_1,
attempt2_syslog_dag_1427546104095_0146_1_post
During a Pig on Tez job the number of succeeded tasks dropped from 380 = 181
as shown below:
{code}
2015-04-15 15:09:56,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 380 Running: 58 Failed: 0
Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 16, diagnostics=
2015-04-15 15:10:16,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 380 Running: 58 Failed: 0
Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 16, diagnostics=
2015-04-15 15:10:36,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 380 Running: 58 Failed: 0
Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 16, diagnostics=
2015-04-15 15:10:56,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 181 Running: 724 Failed:
0 Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 89, diagnostics=
2015-04-15 15:11:16,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 181 Running: 724 Failed:
0 Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 89, diagnostics=
2015-04-15 15:11:36,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 182 Running: 723 Failed:
0 Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 89, diagnostics=
2015-04-15 15:11:56,993 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 184 Running: 721 Failed:
0 Killed: 0 FailedTaskAttempts: 10 KilledTaskAttempts: 89, diagnostics=
2015-04-15 15:12:16,992 [Timer-0] INFO
org.apache.pig.backend.hadoop.executionengine.tez.TezJob - DAG Status:
status=RUNNING, progress=TotalTasks: 905 Succeeded: 186 Running: 719 Failed:
0
{code}
Now this may be because the tasks failed, some certainly did due to space
exceptions having checked the logs, but surely once a task has finished
successfully and is marked as succeeded it cannot then later be removed from
the succeeded count? Perhaps the succeeded counter is incremented too early
before the task results are really saved?
KilledTaskAttempts jumped from 16 = 89 at the same time, but even this
doesn't account for the large drop in number of succeeded tasks.
There was also a noticeable jump in Running tasks from 58 = 724 at the same
time which is suspicious, I'm pretty sure there was no contending job to
finish and release so much more resource to this Tez job, so it's also
unclear how the running count count have jumped up to significantly given the
cluster hardware resources have been the same throughout.
Hari Sekhon
http://www.linkedin.com/in/harisekhon
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2304) InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery
[
https://issues.apache.org/jira/browse/TEZ-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14557994#comment-14557994
]
Jeff Zhang commented on TEZ-2304:
-
In this log, there's only recovery events for
attempt_1428329756093_168563_1_00_006728_1 (attempt_1) but no
attempt_1428329756093_168563_1_00_006728_0 (attempt_0)
It is possible that attempt_0 is killed before it started so there's no any
recovery events for it. We should log the TaskAttemptFinishedEvent even when
there's no TaskAttemptStartedEvent. (link this with TEZ-2456)
In this case, attempt_0 wouldn't be recovered and attempt_1 will be recovered,
and when a new attempt is scheduled its task attempt id would be the same as
the attempt_1, because we create task attempt id by using the attempts.size();
{code}
TaskAttempt attempt = createAttempt(attempts.size());
{code}
That's why we would see the following weird transition ( from NEW to KILLED,
and then form NEW to START_WAIT), actually these are 2 different task attempt
but with the same attempt id, so their state machines are messed up together.
{noformat}
2015-04-09 20:05:42,055 INFO [AsyncDispatcher event handler]
impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt
Transitioned from NEW to KILLED due to event TA_RECOVER
{noformat}
{noformat}
2015-04-09 20:05:45,748 INFO [AsyncDispatcher event handler]
impl.TaskAttemptImpl: attempt_1428329756093_168563_1_00_006728_1 TaskAttempt
Transitioned from NEW to START_WAIT due to event TA_SCHEDULE
{noformat}
InvalidStateTransitonException TA_SCHEDULE at START_WAIT during recovery
Key: TEZ-2304
URL: https://issues.apache.org/jira/browse/TEZ-2304
Project: Apache Tez
Issue Type: Bug
Affects Versions: 0.6.0
Reporter: Jason Lowe
Attachments: 168563_recovery.gz
I saw a Tez AM throw a few InvalidStateTransitonException (sic) instances
during recovery complaining about TA_SCHEDULE arriving at the START_WAIT
state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2450) support async http clients in ordered unordered inputs
[
https://issues.apache.org/jira/browse/TEZ-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558035#comment-14558035
]
TezQA commented on TEZ-2450:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735123/TEZ-2450.4.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 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/735//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/735//console
This message is automatically generated.
support async http clients in ordered unordered inputs
Key: TEZ-2450
URL: https://issues.apache.org/jira/browse/TEZ-2450
Project: Apache Tez
Issue Type: Improvement
Reporter: Rajesh Balamohan
Assignee: Rajesh Balamohan
Attachments: TEZ-2450.1.patch, TEZ-2450.2.WIP.patch,
TEZ-2450.2.patch, TEZ-2450.3.patch, TEZ-2450.4.patch, TEZ-2450.WIP.patch
It will be helpful to switch between JDK other async http impls. For LLAP
scenarios, it would be useful to make http clients interruptible which is
supported in async libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (TEZ-2370) Add stages information to RM UI for debugging / visibility on job progress
[ https://issues.apache.org/jira/browse/TEZ-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon resolved TEZ-2370. -- Resolution: Fixed Fix Version/s: 0.6.0 Ok great thanks, I'll look forward to upgrading to that... I also saw Hortonworks recent announcement for a Tez job view for Ambari which I'm looking forward to trying once it's GA. Add stages information to RM UI for debugging / visibility on job progress -- Key: TEZ-2370 URL: https://issues.apache.org/jira/browse/TEZ-2370 Project: Apache Tez Issue Type: Improvement Components: UI Affects Versions: 0.5.2 Environment: HDP 2.2.0 Reporter: Hari Sekhon Priority: Minor Fix For: 0.6.0 Something that has been bugging me since last year is the difficulty of debugging Tez jobs compared to MapReduce jobs. This is because Resource Manager / Application Master does not display the job stats and stages that we are used to seeing in MapReduce eg. Map and Reduce task counts and progress. I appreciate that Tez is a more flexible framework with a DAG but it would be nice if it could surface the information on the different stages, number of tasks running, completed, failed, killed, successful etc, similar to how Spark does, and the stage breakdown would be useful in understanding what the job is doing at different times, what stage is getting stuck/failing etc. At the moment the only thing available is to trawl the logs or hope to have a console output where some of that information is available, both of which are non-ideal when debugging other's people's jobs after the fact. Hari Sekhon http://www.linkedin.com/in/harisekhon -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Success: TEZ-2450 PreCommit Build #735
Jira: https://issues.apache.org/jira/browse/TEZ-2450
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/735/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3032 lines...]
[INFO] Final Memory: 82M/1227M
[INFO]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735123/TEZ-2450.4.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 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/735//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/735//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
7b8394ac9a2c15dec095fa2bbcfc63d9df199718 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #729
Archived 47 artifacts
Archive block size is 32768
Received 22 blocks and 2199384 bytes
Compression is 24.7%
Took 1 sec
Description set: TEZ-2450
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Updated] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly
[ https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-2481: Attachment: TEZ-2481.3.patch [~pramachandran] Attaching a fresh patch, please review. - The marker wont be visible in IE, also the status wont be visible as the foreign object is also not supported. - Have added all the suggested comments. Tez UI: IE11 - graphical view renders incorrectly - Key: TEZ-2481 URL: https://issues.apache.org/jira/browse/TEZ-2481 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Attachments: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg, TEZ-2481.1.patch, TEZ-2481.2.patch, TEZ-2481.3.patch The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TEZ-2482) Tez UI: IE11 - mouse events not working
Sreenath Somarajapuram created TEZ-2482: --- Summary: Tez UI: IE11 - mouse events not working Key: TEZ-2482 URL: https://issues.apache.org/jira/browse/TEZ-2482 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram In IE 11 mouse events are not delivered to the page anymore at all after a SVG use element which has was under the mouse is removed - https://connect.microsoft.com/IE/feedback/details/796745 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly, mouse events not working
[ https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-2481: Attachment: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg Screenshot of the view from IE. Tez UI: IE11 - graphical view renders incorrectly, mouse events not working --- Key: TEZ-2481 URL: https://issues.apache.org/jira/browse/TEZ-2481 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Attachments: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg, TEZ-2481.1.patch, TEZ-2481.2.patch The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 # In IE 11 mouse events are not delivered to the page anymore at all after a SVG use element which has was under the mouse is removed - https://connect.microsoft.com/IE/feedback/details/796745 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly
[ https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558103#comment-14558103 ] Sreenath Somarajapuram edited comment on TEZ-2481 at 5/25/15 10:58 AM: --- Attaching screenshot of the graph view from IE. was (Author: sreenath): Screenshot of the view from IE. Tez UI: IE11 - graphical view renders incorrectly - Key: TEZ-2481 URL: https://issues.apache.org/jira/browse/TEZ-2481 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Attachments: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg, TEZ-2481.1.patch, TEZ-2481.2.patch The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly, mouse events not working
[ https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558102#comment-14558102 ] Sreenath Somarajapuram commented on TEZ-2481: - - Splitting and creating a new ticket for mouse issue as that need more time. The ticket is https://issues.apache.org/jira/browse/TEZ-2482 - Re submitting patch 2 as the core test failed. Tez UI: IE11 - graphical view renders incorrectly, mouse events not working --- Key: TEZ-2481 URL: https://issues.apache.org/jira/browse/TEZ-2481 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Attachments: TEZ-2481.1.patch, TEZ-2481.2.patch The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 # In IE 11 mouse events are not delivered to the page anymore at all after a SVG use element which has was under the mouse is removed - https://connect.microsoft.com/IE/feedback/details/796745 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly, mouse events not working
[ https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-2481: Description: The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 was: The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 # In IE 11 mouse events are not delivered to the page anymore at all after a SVG use element which has was under the mouse is removed - https://connect.microsoft.com/IE/feedback/details/796745 Tez UI: IE11 - graphical view renders incorrectly, mouse events not working --- Key: TEZ-2481 URL: https://issues.apache.org/jira/browse/TEZ-2481 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Attachments: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg, TEZ-2481.1.patch, TEZ-2481.2.patch The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly
[ https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-2481: Summary: Tez UI: IE11 - graphical view renders incorrectly (was: Tez UI: IE11 - graphical view renders incorrectly, mouse events not working) Tez UI: IE11 - graphical view renders incorrectly - Key: TEZ-2481 URL: https://issues.apache.org/jira/browse/TEZ-2481 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram Attachments: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg, TEZ-2481.1.patch, TEZ-2481.2.patch The issue was because of IE's poor/broken support of css in SVG. # IE doesn't support transform in css like other browsers. This caused the bubbles in a vertex to appear at the origin - https://connect.microsoft.com/IE/feedbackdetail/view/920928 # IE have a broken support for the marker(Arrow on the path). This was causing the links/paths to disappear - https://connect.microsoft.com/IE/feedback/details/801938 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TEZ-2482) Tez UI: IE11 - mouse events not working
[ https://issues.apache.org/jira/browse/TEZ-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram reassigned TEZ-2482: --- Assignee: Sreenath Somarajapuram Tez UI: IE11 - mouse events not working --- Key: TEZ-2482 URL: https://issues.apache.org/jira/browse/TEZ-2482 Project: Apache Tez Issue Type: Bug Reporter: Sreenath Somarajapuram Assignee: Sreenath Somarajapuram In IE 11 mouse events are not delivered to the page anymore at all after a SVG use element which has was under the mouse is removed - https://connect.microsoft.com/IE/feedback/details/796745 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: TEZ-2481 PreCommit Build #736
Jira: https://issues.apache.org/jira/browse/TEZ-2481
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/736/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3015 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735147/TEZ-2481.3.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/736//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/736//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
8bca40fc34a1fe0a3a514aca75356a0152c6a7b3 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #735
Archived 47 artifacts
Archive block size is 32768
Received 8 blocks and 2650066 bytes
Compression is 9.0%
Took 1.1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Commented] (TEZ-2481) Tez UI: IE11 - graphical view renders incorrectly
[
https://issues.apache.org/jira/browse/TEZ-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558149#comment-14558149
]
TezQA commented on TEZ-2481:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735147/TEZ-2481.3.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/736//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/736//console
This message is automatically generated.
Tez UI: IE11 - graphical view renders incorrectly
-
Key: TEZ-2481
URL: https://issues.apache.org/jira/browse/TEZ-2481
Project: Apache Tez
Issue Type: Bug
Reporter: Sreenath Somarajapuram
Assignee: Sreenath Somarajapuram
Attachments: Screen-Shot-2015-05-25-at-4.02.46-PM.jpg,
TEZ-2481.1.patch, TEZ-2481.2.patch, TEZ-2481.3.patch
The issue was because of IE's poor/broken support of css in SVG.
# IE doesn't support transform in css like other browsers. This caused the
bubbles in a vertex to appear at the origin -
https://connect.microsoft.com/IE/feedbackdetail/view/920928
# IE have a broken support for the marker(Arrow on the path). This was
causing the links/paths to disappear -
https://connect.microsoft.com/IE/feedback/details/801938
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-1529) ATS and TezClient integration in secure kerberos enabled cluster
[ https://issues.apache.org/jira/browse/TEZ-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prakash Ramachandran updated TEZ-1529: -- Attachment: TEZ-1529.5.patch addressed comments [~hitesh] for hadoop 2.4 are there any specific tests you were looking at? ATS and TezClient integration in secure kerberos enabled cluster - Key: TEZ-1529 URL: https://issues.apache.org/jira/browse/TEZ-1529 Project: Apache Tez Issue Type: Bug Reporter: Prakash Ramachandran Assignee: Prakash Ramachandran Priority: Blocker Attachments: TEZ-1529-branch6.2.patch, TEZ-1529.1.patch, TEZ-1529.2.patch, TEZ-1529.3.patch, TEZ-1529.4.patch, TEZ-1529.5.patch This is a follow up for TEZ-1495 which address ATS - TezClient integration. however it does not enable it in secure kerberos enabled cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Success: TEZ-1529 PreCommit Build #737
Jira: https://issues.apache.org/jira/browse/TEZ-1529
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/737/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3015 lines...]
[INFO] Final Memory: 84M/1223M
[INFO]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735176/TEZ-1529.5.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 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/737//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/737//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
99e2df120785052de642746ad6abd610f95e849f logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #735
Archived 47 artifacts
Archive block size is 32768
Received 8 blocks and 2657080 bytes
Compression is 9.0%
Took 2 sec
Description set: TEZ-1529
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Commented] (TEZ-1529) ATS and TezClient integration in secure kerberos enabled cluster
[
https://issues.apache.org/jira/browse/TEZ-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558351#comment-14558351
]
TezQA commented on TEZ-1529:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735176/TEZ-1529.5.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 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/737//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/737//console
This message is automatically generated.
ATS and TezClient integration in secure kerberos enabled cluster
-
Key: TEZ-1529
URL: https://issues.apache.org/jira/browse/TEZ-1529
Project: Apache Tez
Issue Type: Bug
Reporter: Prakash Ramachandran
Assignee: Prakash Ramachandran
Priority: Blocker
Attachments: TEZ-1529-branch6.2.patch, TEZ-1529.1.patch,
TEZ-1529.2.patch, TEZ-1529.3.patch, TEZ-1529.4.patch, TEZ-1529.5.patch
This is a follow up for TEZ-1495 which address ATS - TezClient integration.
however it does not enable it in secure kerberos enabled cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2482) Tez UI: IE11 - mouse events not working
[
https://issues.apache.org/jira/browse/TEZ-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558401#comment-14558401
]
Prakash Ramachandran commented on TEZ-2482:
---
few notes
* seems to affect only win7+ie11. IE11 on win8 does not seem to be affected.
* worst case doing a use { pointer-events: none } seems to not freeze.
however this also means the svg elements looks interactivity (click on vertex
to go to details wont work). but would be willing to consider this if no other
solution is viable.
Tez UI: IE11 - mouse events not working
---
Key: TEZ-2482
URL: https://issues.apache.org/jira/browse/TEZ-2482
Project: Apache Tez
Issue Type: Bug
Reporter: Sreenath Somarajapuram
Assignee: Sreenath Somarajapuram
In IE 11 mouse events are not delivered to the page anymore at all after a
SVG use element which has was under the mouse is removed -
https://connect.microsoft.com/IE/feedback/details/796745
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TEZ-2483) Tez should close task if processor fail
Daniel Dai created TEZ-2483: --- Summary: Tez should close task if processor fail Key: TEZ-2483 URL: https://issues.apache.org/jira/browse/TEZ-2483 Project: Apache Tez Issue Type: Bug Reporter: Daniel Dai Fix For: 0.7.1 The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this creates a problem since Pig client cannot remove the input file. In general, if a task fail, Tez shall close all input/output handles in cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly right now. Attach a demo patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2483) Tez should close task if processor fail
[ https://issues.apache.org/jira/browse/TEZ-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated TEZ-2483: Attachment: TEZ-2483-1.patch Tez should close task if processor fail --- Key: TEZ-2483 URL: https://issues.apache.org/jira/browse/TEZ-2483 Project: Apache Tez Issue Type: Bug Reporter: Daniel Dai Fix For: 0.7.1 Attachments: TEZ-2483-1.patch The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this creates a problem since Pig client cannot remove the input file. In general, if a task fail, Tez shall close all input/output handles in cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly right now. Attach a demo patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2483) Tez should close task if processor fail
[ https://issues.apache.org/jira/browse/TEZ-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558606#comment-14558606 ] Daniel Dai commented on TEZ-2483: - This is revealed by Pig UT failure: TestStoreLocal.testSuccessFileCreation2 Tez should close task if processor fail --- Key: TEZ-2483 URL: https://issues.apache.org/jira/browse/TEZ-2483 Project: Apache Tez Issue Type: Bug Reporter: Daniel Dai Fix For: 0.7.1 Attachments: TEZ-2483-1.patch The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this creates a problem since Pig client cannot remove the input file. In general, if a task fail, Tez shall close all input/output handles in cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly right now. Attach a demo patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TEZ-2483) Tez should close task if processor fail
[ https://issues.apache.org/jira/browse/TEZ-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558625#comment-14558625 ] Jeff Zhang edited comment on TEZ-2483 at 5/26/15 2:32 AM: -- Thanks [~daijy] I upload a new patch with minor change. close() can only be invoked when task in the state of RUNNING (after initialized). [~sseth] [~rajesh.balamohan] Please help review was (Author: zjffdu): Thanks [~daijy] I upload a new patch with minor change. close() can only be invoked when task in the state of RUNNING (after initialized). Tez should close task if processor fail --- Key: TEZ-2483 URL: https://issues.apache.org/jira/browse/TEZ-2483 Project: Apache Tez Issue Type: Bug Reporter: Daniel Dai Fix For: 0.7.1 Attachments: TEZ-2483-1.patch, TEZ-2483-2.patch The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this creates a problem since Pig client cannot remove the input file. In general, if a task fail, Tez shall close all input/output handles in cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly right now. Attach a demo patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2483) Tez should close task if processor fail
[ https://issues.apache.org/jira/browse/TEZ-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated TEZ-2483: Attachment: TEZ-2483-2.patch Thanks [~daijy] I upload a new patch with minor change. close() can only be invoked when task in the state of RUNNING (after initialized). Tez should close task if processor fail --- Key: TEZ-2483 URL: https://issues.apache.org/jira/browse/TEZ-2483 Project: Apache Tez Issue Type: Bug Reporter: Daniel Dai Fix For: 0.7.1 Attachments: TEZ-2483-1.patch, TEZ-2483-2.patch The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this creates a problem since Pig client cannot remove the input file. In general, if a task fail, Tez shall close all input/output handles in cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly right now. Attach a demo patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2483) Tez should close task if processor fail
[ https://issues.apache.org/jira/browse/TEZ-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558631#comment-14558631 ] Rajesh Balamohan commented on TEZ-2483: --- In normal cases, it would throw exception in the finally block as close() would have been called anyways. Even though it is harmless, it might be easier to add this to task.cleanup() by checking this.state.equals(State.CLOSED). lgtm otherwise. Tez should close task if processor fail --- Key: TEZ-2483 URL: https://issues.apache.org/jira/browse/TEZ-2483 Project: Apache Tez Issue Type: Bug Reporter: Daniel Dai Fix For: 0.7.1 Attachments: TEZ-2483-1.patch, TEZ-2483-2.patch The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this creates a problem since Pig client cannot remove the input file. In general, if a task fail, Tez shall close all input/output handles in cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly right now. Attach a demo patch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: TEZ-2483 PreCommit Build #738
Jira: https://issues.apache.org/jira/browse/TEZ-2483
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/738/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2141 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735239/TEZ-2483-2.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.runtime.task.TestTaskExecution
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/738//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/738//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
3c8e7529d1761f7d6c4c28d8d328b4b7bcfcc954 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-TEZ-Build #737
Archived 47 artifacts
Archive block size is 32768
Received 10 blocks and 2521689 bytes
Compression is 11.5%
Took 1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
2 tests failed.
REGRESSION:
org.apache.tez.runtime.task.TestTaskExecution.testMultipleSuccessfulTasks
Error Message:
org.apache.tez.dag.api.TezException: java.lang.IllegalStateException: Can only
run while in RUNNING state. Current: CLOSED
Stack Trace:
java.util.concurrent.ExecutionException: org.apache.tez.dag.api.TezException:
java.lang.IllegalStateException: Can only run while in RUNNING state. Current:
CLOSED
at
com.google.common.base.Preconditions.checkState(Preconditions.java:145)
at
org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.close(LogicalIOProcessorRuntimeTask.java:342)
at
org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable$1.run(TezTaskRunner.java:250)
at
org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable$1.run(TezTaskRunner.java:171)
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:1628)
at
org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable.callInternal(TezTaskRunner.java:171)
at
org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable.callInternal(TezTaskRunner.java:167)
at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
REGRESSION:
org.apache.tez.runtime.task.TestTaskExecution.testSingleSuccessfulTask
Error Message:
org.apache.tez.dag.api.TezException: java.lang.IllegalStateException: Can only
run while in RUNNING state. Current: CLOSED
Stack Trace:
java.util.concurrent.ExecutionException: org.apache.tez.dag.api.TezException:
java.lang.IllegalStateException: Can only run while in RUNNING state. Current:
CLOSED
at
[jira] [Commented] (TEZ-2483) Tez should close task if processor fail
[
https://issues.apache.org/jira/browse/TEZ-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558637#comment-14558637
]
TezQA commented on TEZ-2483:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12735239/TEZ-2483-2.patch
against master revision 87156be.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.runtime.task.TestTaskExecution
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/738//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/738//console
This message is automatically generated.
Tez should close task if processor fail
---
Key: TEZ-2483
URL: https://issues.apache.org/jira/browse/TEZ-2483
Project: Apache Tez
Issue Type: Bug
Reporter: Daniel Dai
Fix For: 0.7.1
Attachments: TEZ-2483-1.patch, TEZ-2483-2.patch
The symptom is if PigProcessor fail, MRInput is not closed. On Windows, this
creates a problem since Pig client cannot remove the input file.
In general, if a task fail, Tez shall close all input/output handles in
cleanup. MROutput is closed in MROutput.abort() which Pig invokes explicitly
right now. Attach a demo patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2307) DAGAppMaster may still be in RUNNING when DAG is finished
[
https://issues.apache.org/jira/browse/TEZ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14558699#comment-14558699
]
Jeff Zhang commented on TEZ-2307:
-
[~mitdesai] It is not easy to reproduce it. It happens randomly. I check the
code that it is possible to happen. The reason is that DAG's state machine may
already transition to FINISHED state, that means client also know that DAG is
completed and may submit a new dag. But at this time, DAGAppMaster may haven't
know the DAG is completed. so will cause the above error. I link this ticket
with TEZ-1273, suppose after TEZ-1273, it can be resolved.
DAGAppMaster may still be in RUNNING when DAG is finished
-
Key: TEZ-2307
URL: https://issues.apache.org/jira/browse/TEZ-2307
Project: Apache Tez
Issue Type: Bug
Reporter: Jeff Zhang
It is possible that DAG is finished while DAGAppMaster is still in RUNNING,
in this case the next submission of dag will cause the following error:
{code}
2015-04-10 06:01:50,369 INFO [IPC Server handler 0 on 46821] ipc.Server
(Server.java:run(2070)) - IPC Server handler 0 on 46821, call
org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPB.submitDAG
from 10.0.0.223:48581 Call#411 Retry#0
org.apache.tez.dag.api.TezException: App master already running a DAG
at
org.apache.tez.dag.app.DAGAppMaster.submitDAGToAppMaster(DAGAppMaster.java:1131)
at
org.apache.tez.dag.api.client.DAGClientHandler.submitDAG(DAGClientHandler.java:118)
at
org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolBlockingPBServerImpl.submitDAG(DAGClientAMProtocolBlockingPBServerImpl.java:163)
at
org.apache.tez.dag.api.client.rpc.DAGClientAMProtocolRPC$DAGClientAMProtocol$2.callBlockingMethod(DAGClientAMProtocolRPC.java:7471)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:616)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:969)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2049)
at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2045)
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:2043)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
