[jira] [Commented] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[
https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514964#comment-14514964
]
Hitesh Shah commented on TEZ-2259:
--
Not sure what is off with the build. Console logs show a successful run:
{code}
INFO] tez ... SUCCESS [ 1.048 s]
[INFO] tez-api ... SUCCESS [ 39.822 s]
[INFO] tez-common SUCCESS [ 3.114 s]
[INFO] tez-runtime-internals . SUCCESS [ 10.713 s]
[INFO] tez-runtime-library ... SUCCESS [01:13 min]
[INFO] tez-mapreduce . SUCCESS [ 25.778 s]
[INFO] tez-examples .. SUCCESS [ 0.330 s]
[INFO] tez-dag ... SUCCESS [02:04 min]
[INFO] tez-tests . SUCCESS [24:57 min]
[INFO] tez-ui SUCCESS [ 14.317 s]
[INFO] tez-plugins ... SUCCESS [ 0.033 s]
[INFO] tez-yarn-timeline-history . SUCCESS [ 54.781 s]
[INFO] tez-yarn-timeline-history-with-acls ... SUCCESS [01:03 min]
[INFO] tez-mbeans-resource-calculator SUCCESS [ 0.970 s]
[INFO] tez-dist .. SUCCESS [ 12.728 s]
[INFO] Tez ... SUCCESS [ 0.032 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 32:04 min
[INFO] Finished at: 2015-04-27T20:13:33+00:00
[INFO] Final Memory: 68M/814M
[INFO]
{code}
{code}
[INFO] --- maven-surefire-plugin:2.14.1:test (default-test) @ tez-tests ---
[INFO] Surefire report directory:
/home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build@2/tez-tests/target/surefire-reports
---
T E S T S
---
---
T E S TTests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
209.311 sec
Running org.apache.tez.test.Tests run: 2, FaTests run: 2, Failures: 0, Errors:
0, Skipped: 0, Time elapsed: 91.521 sec
Running org.apache.tez.test.TestTests run: 22, FailurTests run: 2, Failures: 0,
Errors: 0, Skipped: 0, Time elapsed: 143.722 sec
Running org.apache.tez.teTests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time
elapsed: 79.795 sec
Running org.apache.tez.test.TestAMRecovery
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 267.144 sec
Running org.apache.tez.test.TestTezJobs
Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 211.42 sec
Running org.apache.tez.test.TestDAGRecovery
ests run: 77, Failures: 0, Errors: 0, Skipped: 0
{code}
- some munging of the output seems to exist.
Ran tests locally and confirmed no failures.
Push additional data to Timeline for Recovery for better consumption in UI
--
Key: TEZ-2259
URL: https://issues.apache.org/jira/browse/TEZ-2259
Project: Apache Tez
Issue Type: Bug
Reporter: Hitesh Shah
Assignee: Hitesh Shah
Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch,
TEZ-2259.4.patch
Some things I can think of:
- applicationAttemptId in which the dag was submitted
- appAttemptId in which the dag was completed
Above provides implicit information on how many app attempts the dag spanned
( and therefore recovered how many times ).
- Maybe an implicit event mentioning that the DAG was recovered and in
which attempt it was recovered. Possibly add information on what state was
recovered?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14491084#comment-14491084 ] Prakash Ramachandran commented on TEZ-2259: --- +1 LGTM Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[
https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14490416#comment-14490416
]
TezQA commented on TEZ-2259:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12724654/TEZ-2259.3.patch
against master revision c8ef244.
{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:red}-1 core tests{color}. The following test timeouts occurred in :
org.apache.tez.test.TestSecureShuffle
org.apache.tez.test.TestFaultTolerance
Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/442//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/442//console
This message is automatically generated.
Push additional data to Timeline for Recovery for better consumption in UI
--
Key: TEZ-2259
URL: https://issues.apache.org/jira/browse/TEZ-2259
Project: Apache Tez
Issue Type: Bug
Reporter: Hitesh Shah
Assignee: Hitesh Shah
Attachments: TEZ-2259.1.patch, TEZ-2259.2.patch, TEZ-2259.3.patch
Some things I can think of:
- applicationAttemptId in which the dag was submitted
- appAttemptId in which the dag was completed
Above provides implicit information on how many app attempts the dag spanned
( and therefore recovered how many times ).
- Maybe an implicit event mentioning that the DAG was recovered and in
which attempt it was recovered. Possibly add information on what state was
recovered?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389485#comment-14389485 ] Hitesh Shah commented on TEZ-2259: -- FWIW, once attempt ids are known, the DAG logs can be obtained by find the log links from the data obtained from http://RM:8088/ws/v1/cluster/apps/app id/appattempts Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2259) Push additional data to Timeline for Recovery for better consumption in UI
[ https://issues.apache.org/jira/browse/TEZ-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14389481#comment-14389481 ] Hitesh Shah commented on TEZ-2259: -- \cc [~zjffdu] Push additional data to Timeline for Recovery for better consumption in UI -- Key: TEZ-2259 URL: https://issues.apache.org/jira/browse/TEZ-2259 Project: Apache Tez Issue Type: Bug Reporter: Hitesh Shah Assignee: Hitesh Shah Some things I can think of: - applicationAttemptId in which the dag was submitted - appAttemptId in which the dag was completed Above provides implicit information on how many app attempts the dag spanned ( and therefore recovered how many times ). - Maybe an implicit event mentioning that the DAG was recovered and in which attempt it was recovered. Possibly add information on what state was recovered? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
