[jira] [Assigned] (TEZ-2307) Possible wrong error message when submitting new dag
[
https://issues.apache.org/jira/browse/TEZ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang reassigned TEZ-2307:
---
Assignee: Jeff Zhang
> Possible wrong error message when submitting new dag
>
>
> Key: TEZ-2307
> URL: https://issues.apache.org/jira/browse/TEZ-2307
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: TEZ-2307-1.patch
>
>
> In the following 2 cases, AM would propagate wrong error message to client
> ("App master already running a DAG")
> * The last dag is completed but AM is still in RUNNING state
> * AM is in shutting down.
> {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)
[jira] [Updated] (TEZ-2307) Possible wrong error message when submitting new dag
[
https://issues.apache.org/jira/browse/TEZ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated TEZ-2307:
Attachment: TEZ-2307-1.patch
> Possible wrong error message when submitting new dag
>
>
> Key: TEZ-2307
> URL: https://issues.apache.org/jira/browse/TEZ-2307
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jeff Zhang
> Attachments: TEZ-2307-1.patch
>
>
> In the following 2 cases, AM would propagate wrong error message to client
> ("App master already running a DAG")
> * The last dag is completed but AM is still in RUNNING state
> * AM is in shutting down.
> {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)
[jira] [Updated] (TEZ-2307) Possible wrong error message when submitting new dag
[
https://issues.apache.org/jira/browse/TEZ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated TEZ-2307:
Target Version/s: 0.7.1
Fix Version/s: (was: 0.8.2)
(was: 0.7.1)
> Possible wrong error message when submitting new dag
>
>
> Key: TEZ-2307
> URL: https://issues.apache.org/jira/browse/TEZ-2307
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: TEZ-2307-1.patch
>
>
> In the following 2 cases, AM would propagate wrong error message to client
> ("App master already running a DAG")
> * The last dag is completed but AM is still in RUNNING state
> * AM is in shutting down.
> {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)
Failed: TEZ-2978 PreCommit Build #1410
Jira: https://issues.apache.org/jira/browse/TEZ-2978
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1410/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3666 lines...]
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :tez-tests
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781117/TEZ-2978.1.txt
against master revision d5c9649.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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 3.0.1) 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.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1410//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1410//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
e0fda68d9fba339ec7b161fb1541d1e39b191f1b logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
14 tests failed.
FAILED: org.apache.tez.test.TestFaultTolerance.testNoProgress
Error Message:
expected: but was:
Stack Trace:
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:141)
at
org.apache.tez.test.TestFaultTolerance.testNoProgress(TestFaultTolerance.java:777)
FAILED:
org.apache.tez.test.TestFaultTolerance.testInputFailureCausesRerunAttemptWithinMaxAttemptSuccess
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:784)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:129)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
org.apache.tez.test.TestFaultTolerance.testInputFailureCausesRerunAttemptWithinMaxAttemptSuccess(TestFaultTolerance.java:476)
FAILED: org.apache.tez.test.TestFaultTolerance.testBasicInputFailureWithoutExit
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:784)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:129)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
[jira] [Commented] (TEZ-2978) Add an option to allow small splits early on in TezSplitGrouper
[
https://issues.apache.org/jira/browse/TEZ-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089943#comment-15089943
]
TezQA commented on TEZ-2978:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781117/TEZ-2978.1.txt
against master revision d5c9649.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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 3.0.1) 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.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1410//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1410//console
This message is automatically generated.
> Add an option to allow small splits early on in TezSplitGrouper
> ---
>
> Key: TEZ-2978
> URL: https://issues.apache.org/jira/browse/TEZ-2978
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: TEZ-2978.1.txt
>
>
> In certain cases, allowing the last few splits to be 'small' - smaller than
> the requested size is beneficial, and can end up creating fewer splits. Also
> this results in all splits having some form of locality information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-2865 PreCommit Build #1412
Jira: https://issues.apache.org/jira/browse/TEZ-2865
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1412/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3757 lines...]
[INFO]
[INFO] Total time: 50:27 min
[INFO] Finished at: 2016-01-08T21:38:47+00:00
[INFO] Final Memory: 89M/1117M
[INFO]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781282/TEZ-2865.1.txt
against master revision d5c9649.
{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 3.0.1) 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/1412//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1412//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c2a9bdb1838fa64e631caefaaee9d029ab91b028 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Commented] (TEZ-2129) Task and Attempt views should contain links to the logs
[ https://issues.apache.org/jira/browse/TEZ-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089781#comment-15089781 ] Jonathan Eagles commented on TEZ-2129: -- Thanks, [~Sreenath]. committing to master and branch-0.7. > Task and Attempt views should contain links to the logs > --- > > Key: TEZ-2129 > URL: https://issues.apache.org/jira/browse/TEZ-2129 > Project: Apache Tez > Issue Type: Improvement > Components: UI >Reporter: Kevin J. Price >Assignee: Jonathan Eagles >Priority: Minor > Attachments: TEZ-2129.1.patch, TEZ-2129.2.patch > > > Currently, the actual task or attempt view does not contain a link to get to > the container logs. That link exists on the list view page, but not the view > page for a specific task/attempt. There should be a direct link to the logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: TEZ-2669 PreCommit Build #1411
Jira: https://issues.apache.org/jira/browse/TEZ-2669
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1411/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3715 lines...]
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :tez-tests
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781121/TEZ-2669.3.txt
against master revision d5c9649.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 20 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 3.0.1) 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.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1411//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1411//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c333ffde6200b6196425adb90fb26dfebabe2c44 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
14 tests failed.
FAILED: org.apache.tez.test.TestFaultTolerance.testNoProgress
Error Message:
expected: but was:
Stack Trace:
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:141)
at
org.apache.tez.test.TestFaultTolerance.testNoProgress(TestFaultTolerance.java:777)
FAILED:
org.apache.tez.test.TestFaultTolerance.testInputFailureCausesRerunAttemptWithinMaxAttemptSuccess
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:784)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:129)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
org.apache.tez.test.TestFaultTolerance.testInputFailureCausesRerunAttemptWithinMaxAttemptSuccess(TestFaultTolerance.java:476)
FAILED: org.apache.tez.test.TestFaultTolerance.testBasicInputFailureWithoutExit
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:784)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:129)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
[jira] [Commented] (TEZ-2669) Propagation of errors from plugins to the AM for error reporting
[
https://issues.apache.org/jira/browse/TEZ-2669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089966#comment-15089966
]
TezQA commented on TEZ-2669:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781121/TEZ-2669.3.txt
against master revision d5c9649.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 20 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 3.0.1) 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.test.TestFaultTolerance
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1411//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1411//console
This message is automatically generated.
> Propagation of errors from plugins to the AM for error reporting
>
>
> Key: TEZ-2669
> URL: https://issues.apache.org/jira/browse/TEZ-2669
> Project: Apache Tez
> Issue Type: Sub-task
>Affects Versions: 0.8.0-alpha
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
>Priority: Blocker
> Attachments: TEZ-2669.1.txt, TEZ-2669.2.txt, TEZ-2669.3.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-2997) Tez UI: Support searches by CallerContext ID for DAGs
[ https://issues.apache.org/jira/browse/TEZ-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated TEZ-2997: Target Version/s: 0.7.1 (was: 0.7.1, 0.8.2) > Tez UI: Support searches by CallerContext ID for DAGs > - > > Key: TEZ-2997 > URL: https://issues.apache.org/jira/browse/TEZ-2997 > Project: Apache Tez > Issue Type: Bug >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: TEZ-2997-branch-0.7.patch, TEZ-2997.1.patch, > TEZ-2997.2.patch, TEZ-2997.3.patch > > > CallerContext info is added to ATS and is used by Hive to add the query Id > info but there is no way to search based on these ids in the Tez UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2865) Reduce default timeout for containers and tasks
[ https://issues.apache.org/jira/browse/TEZ-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated TEZ-2865: Attachment: TEZ-2865.1.txt Trivial patch. [~zjffdu], [~hitesh] - please review. > Reduce default timeout for containers and tasks > --- > > Key: TEZ-2865 > URL: https://issues.apache.org/jira/browse/TEZ-2865 > Project: Apache Tez > Issue Type: Improvement >Reporter: Siddharth Seth > Attachments: TEZ-2865.1.txt > > > Currently set to 5 minutes, which is very long. A minute or less should be > sufficient to recover from intermittent issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-2594) Fix licensing and notice file for minimal tarball
[ https://issues.apache.org/jira/browse/TEZ-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Seth updated TEZ-2594: Target Version/s: 0.7.1 (was: 0.7.1, 0.8.2) > Fix licensing and notice file for minimal tarball > - > > Key: TEZ-2594 > URL: https://issues.apache.org/jira/browse/TEZ-2594 > Project: Apache Tez > Issue Type: Task >Reporter: Hitesh Shah >Assignee: Hitesh Shah > Attachments: TEZ-2594.1.patch > > > Minimal tarball needs its own license and notice file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2865) Reduce default timeout for containers and tasks
[
https://issues.apache.org/jira/browse/TEZ-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089986#comment-15089986
]
TezQA commented on TEZ-2865:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781282/TEZ-2865.1.txt
against master revision d5c9649.
{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 3.0.1) 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/1412//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1412//console
This message is automatically generated.
> Reduce default timeout for containers and tasks
> ---
>
> Key: TEZ-2865
> URL: https://issues.apache.org/jira/browse/TEZ-2865
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: Siddharth Seth
> Attachments: TEZ-2865.1.txt
>
>
> Currently set to 5 minutes, which is very long. A minute or less should be
> sufficient to recover from intermittent issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-2164 PreCommit Build #1418
Jira: https://issues.apache.org/jira/browse/TEZ-2164
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1418/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 21 lines...]
[PreCommit-TEZ-Build] $ /bin/bash /tmp/hudson8549903059909200939.sh
Running in Jenkins mode
==
==
Testing patch for TEZ-2164.
==
==
HEAD is now at 85637c6 TEZ-2129. Task and Attempt views should contain links to
the logs (jeagles)
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
Current branch master is up to date.
TEZ-2164 patch is being downloaded at Fri Jan 8 22:18:34 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12755022/TEZ-2164.4.patch
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12755022/TEZ-2164.4.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1418//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2829ff434dda58396b8563480e407bdb95bc6e91 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Publisher 'Publish JUnit test result report' failed: No test report
files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
[jira] [Commented] (TEZ-2164) Shade the guava version used by Tez and move to guava-18
[
https://issues.apache.org/jira/browse/TEZ-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090047#comment-15090047
]
TezQA commented on TEZ-2164:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12755022/TEZ-2164.4.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1418//console
This message is automatically generated.
> Shade the guava version used by Tez and move to guava-18
>
>
> Key: TEZ-2164
> URL: https://issues.apache.org/jira/browse/TEZ-2164
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: Siddharth Seth
>Assignee: Hitesh Shah
>Priority: Critical
> Attachments: TEZ-2164.3.patch, TEZ-2164.4.patch,
> TEZ-2164.wip.2.patch, allow-guava-16.0.1.patch
>
>
> Should allow us to upgrade to a newer version without shipping a guava
> dependency.
> Would be good to do this in 0.7 so that we stop shipping guava as early as
> possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-1273) Refactor DAGAppMaster to state machine based
[
https://issues.apache.org/jira/browse/TEZ-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090046#comment-15090046
]
TezQA commented on TEZ-1273:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12740332/TEZ-1273-10.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1417//console
This message is automatically generated.
> Refactor DAGAppMaster to state machine based
>
>
> Key: TEZ-1273
> URL: https://issues.apache.org/jira/browse/TEZ-1273
> Project: Apache Tez
> Issue Type: Improvement
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: DAGAppMaster_3.pdf, DAGAppMaster_4.pdf,
> DAGAppMaster_5.pdf, TEZ-1273-10.patch, TEZ-1273-3.patch, TEZ-1273-4.patch,
> TEZ-1273-5.patch, TEZ-1273-6.patch, TEZ-1273-7.patch, TEZ-1273-8.patch,
> TEZ-1273-9.patch, Tez-1273-2.patch, Tez-1273.patch, dag_app_master.pdf,
> dag_app_master2.pdf
>
>
> Almost all our entities (Vertex, Task etc) are state machine based and
> written using a formal state machine. But DAGAppMaster is not written on a
> formal state machine even though it has a state machine based behavior. This
> jira is for refactoring it into state machine based
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-993 PreCommit Build #1416
Jira: https://issues.apache.org/jira/browse/TEZ-993
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1416/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 24 lines...]
==
==
Testing patch for TEZ-993.
==
==
HEAD is now at 85637c6 TEZ-2129. Task and Attempt views should contain links to
the logs (jeagles)
Previous HEAD position was 85637c6... TEZ-2129. Task and Attempt views should
contain links to the logs (jeagles)
Switched to branch 'master'
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
(use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded master to 85637c61a2cf2c16c147826b2908d459a7b1b7cf.
TEZ-993 patch is being downloaded at Fri Jan 8 22:18:13 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12695488/TEZ-993-5.patch
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695488/TEZ-993-5.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1416//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
0f0cda2c9eb7224e639f53adfd63236150fa75af logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Publisher 'Publish JUnit test result report' failed: No test report
files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: TEZ-391 PreCommit Build #1413
Jira: https://issues.apache.org/jira/browse/TEZ-391
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1413/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 24 lines...]
==
==
Testing patch for TEZ-391.
==
==
HEAD is now at 85637c6 TEZ-2129. Task and Attempt views should contain links to
the logs (jeagles)
Previous HEAD position was 85637c6... TEZ-2129. Task and Attempt views should
contain links to the logs (jeagles)
Switched to branch 'master'
Your branch is behind 'origin/master' by 3 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded master to 85637c61a2cf2c16c147826b2908d459a7b1b7cf.
TEZ-391 patch is being downloaded at Fri Jan 8 22:15:04 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12734397/TEZ-391-WIP-7.patch
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12734397/TEZ-391-WIP-7.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1413//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
08de1d4df2d52b418823cd3a5caac7ea9d9b4d20 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Publisher 'Publish JUnit test result report' failed: No test report
files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: TEZ-1019 PreCommit Build #1414
Jira: https://issues.apache.org/jira/browse/TEZ-1019
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1414/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 21 lines...]
[PreCommit-TEZ-Build] $ /bin/bash /tmp/hudson4928642021658112962.sh
Running in Jenkins mode
==
==
Testing patch for TEZ-1019.
==
==
HEAD is now at 85637c6 TEZ-2129. Task and Attempt views should contain links to
the logs (jeagles)
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
Current branch master is up to date.
TEZ-1019 patch is being downloaded at Fri Jan 8 22:15:12 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12697692/TEZ-1019-5.patch
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12697692/TEZ-1019-5.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1414//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c9cdb8cb6dda6658d36336b15b661693007944a6 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Publisher 'Publish JUnit test result report' failed: No test report
files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: TEZ-1273 PreCommit Build #1417
Jira: https://issues.apache.org/jira/browse/TEZ-1273
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1417/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 21 lines...]
[PreCommit-TEZ-Build] $ /bin/bash /tmp/hudson4518676329398381774.sh
Running in Jenkins mode
==
==
Testing patch for TEZ-1273.
==
==
HEAD is now at 85637c6 TEZ-2129. Task and Attempt views should contain links to
the logs (jeagles)
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
Current branch master is up to date.
TEZ-1273 patch is being downloaded at Fri Jan 8 22:18:24 UTC 2016 from
http://issues.apache.org/jira/secure/attachment/12740332/TEZ-1273-10.patch
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12740332/TEZ-1273-10.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1417//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
142d5379e0c60cdd3388d81fbc4a7061fd3a5cf5 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Publisher 'Publish JUnit test result report' failed: No test report
files were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
No tests ran.
[jira] [Commented] (TEZ-993) Remove application logic from RecoveryService
[
https://issues.apache.org/jira/browse/TEZ-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090045#comment-15090045
]
TezQA commented on TEZ-993:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695488/TEZ-993-5.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1416//console
This message is automatically generated.
> Remove application logic from RecoveryService
> -
>
> Key: TEZ-993
> URL: https://issues.apache.org/jira/browse/TEZ-993
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Bikas Saha
>Assignee: Jeff Zhang
> Attachments: TEZ-993-3.patch, TEZ-993-4.patch, TEZ-993-5.patch,
> Tez-993-2.patch, Tez-993.patch
>
>
> Currently RecoveryService storage logic knows a lot about the DAG like which
> dag is pre-warm and does not need to be stored, which events needs special
> treatment etc. This kind of logic couples the DAG and the storage more than
> is probably necessary and can be a source of complications down the road. The
> storage should ideally be simply storing a sequence of arbitrary records
> delimited by a marker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-1869 PreCommit Build #1415
Jira: https://issues.apache.org/jira/browse/TEZ-1869
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1415/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3598 lines...]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :tez-dag
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12688151/TEZ-1869.1.txt
against master revision 85637c6.
{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 3.0.1) 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.test.TestFaultTolerance
org.apache.tez.dag.app.dag.impl.TestCommit
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1415//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1415//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
6b4d94a4db8d5cb754f7174eac57f9a7d98fc66c logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
8 tests failed.
FAILED:
org.apache.tez.dag.app.dag.impl.TestCommit.testDAGCommitSucceeded3_OnVertexSuccess
Error Message:
null
Stack Trace:
java.lang.NullPointerException: null
at
org.apache.tez.dag.app.dag.impl.TestCommit$MockHistoryEventHandler.verifyVertexGroupCommitStartedEvent(TestCommit.java:2008)
at
org.apache.tez.dag.app.dag.impl.TestCommit.testDAGCommitSucceeded3_OnVertexSuccess(TestCommit.java:1197)
FAILED: org.apache.tez.test.TestFaultTolerance.testRandomFailingInputs
Error Message:
expected: but was:
Stack Trace:
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:141)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
org.apache.tez.test.TestFaultTolerance.testRandomFailingInputs(TestFaultTolerance.java:763)
FAILED: org.apache.tez.test.TestFaultTolerance.testBasicInputFailureWithExit
Error Message:
TezSession has already shutdown. No cluster diagnostics found.
Stack Trace:
org.apache.tez.dag.api.SessionNotRunning: TezSession has already shutdown. No
cluster diagnostics found.
at org.apache.tez.client.TezClient.waitTillReady(TezClient.java:784)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:129)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:124)
at
org.apache.tez.test.TestFaultTolerance.runDAGAndVerify(TestFaultTolerance.java:120)
at
org.apache.tez.test.TestFaultTolerance.testBasicInputFailureWithExit(TestFaultTolerance.java:261)
FAILED:
[jira] [Commented] (TEZ-1869) Exclude tez-ui war / other dependencies from tez.tar.gz
[
https://issues.apache.org/jira/browse/TEZ-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090174#comment-15090174
]
TezQA commented on TEZ-1869:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12688151/TEZ-1869.1.txt
against master revision 85637c6.
{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 3.0.1) 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.test.TestFaultTolerance
org.apache.tez.dag.app.dag.impl.TestCommit
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1415//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1415//console
This message is automatically generated.
> Exclude tez-ui war / other dependencies from tez.tar.gz
> ---
>
> Key: TEZ-1869
> URL: https://issues.apache.org/jira/browse/TEZ-1869
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
>Reporter: Siddharth Seth
>Assignee: Siddharth Seth
> Attachments: TEZ-1869.1.txt
>
>
> tez.tar.gz is meant to be uploaded to HDFS and configured in tez.lib.uris.
> The war file, along with any dependencies should not be required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TEZ-3027) Tez UI 2: Add header and footer elements
[ https://issues.apache.org/jira/browse/TEZ-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3027: Attachment: TEZ-3027.1.patch - Added header & footer - Breadcrumb component was created and added to em-helpers addon, also the same was integrated into the UI - Added timezone, version & help > Tez UI 2: Add header and footer elements > > > Key: TEZ-3027 > URL: https://issues.apache.org/jira/browse/TEZ-3027 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3027.1.patch > > > - Add header and footer elements to application template > - Create breadcrumb component and add it to header > - Add timezone display to the footer > - Add help link & version on header > - Add font awesome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3027) Tez UI 2: Add header and footer elements
[ https://issues.apache.org/jira/browse/TEZ-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3027: Attachment: TEZ-3027.2.patch Adding application controller. > Tez UI 2: Add header and footer elements > > > Key: TEZ-3027 > URL: https://issues.apache.org/jira/browse/TEZ-3027 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3027.1.patch, TEZ-3027.2.patch > > > - Add header and footer elements to application template > - Create breadcrumb component and add it to header > - Add timezone display to the footer > - Add help link & version on header > - Add font awesome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3027) Tez UI 2: Add header and footer elements
[ https://issues.apache.org/jira/browse/TEZ-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3027: Attachment: logo.png favicon.png Adding assets to be added @ tez/tez-ui2/src/main/webapp/public/assets/images/ > Tez UI 2: Add header and footer elements > > > Key: TEZ-3027 > URL: https://issues.apache.org/jira/browse/TEZ-3027 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3027.1.patch, TEZ-3027.2.patch, favicon.png, logo.png > > > - Add header and footer elements to application template > - Create breadcrumb component and add it to header > - Add timezone display to the footer > - Add help link & version on header > - Add font awesome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TEZ-3027) Tez UI 2: Add header and footer elements
[ https://issues.apache.org/jira/browse/TEZ-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090480#comment-15090480 ] Sreenath Somarajapuram edited comment on TEZ-3027 at 1/9/16 7:45 AM: - - Added header & footer - Breadcrumb component was created and added to em-helpers addon, also the same was integrated into the UI - Added timezone, version & help - Added logo and favicon was (Author: sreenath): - Added header & footer - Breadcrumb component was created and added to em-helpers addon, also the same was integrated into the UI - Added timezone, version & help > Tez UI 2: Add header and footer elements > > > Key: TEZ-3027 > URL: https://issues.apache.org/jira/browse/TEZ-3027 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3027.1.patch, TEZ-3027.2.patch, favicon.png, logo.png > > > - Add header and footer elements to application template > - Create breadcrumb component and add it to header > - Add timezone display to the footer > - Add help link & version on header > - Add font awesome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TEZ-3027) Tez UI 2: Add header and footer elements
[ https://issues.apache.org/jira/browse/TEZ-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram resolved TEZ-3027. - Resolution: Fixed Committed to TEZ-2980 > Tez UI 2: Add header and footer elements > > > Key: TEZ-3027 > URL: https://issues.apache.org/jira/browse/TEZ-3027 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Sreenath Somarajapuram >Assignee: Sreenath Somarajapuram > Attachments: TEZ-3027.1.patch, TEZ-3027.2.patch, favicon.png, logo.png > > > - Add header and footer elements to application template > - Create breadcrumb component and add it to header > - Add timezone display to the footer > - Add help link & version on header > - Add font awesome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2307) Possible wrong error message when submitting new dag
[
https://issues.apache.org/jira/browse/TEZ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090008#comment-15090008
]
Siddharth Seth commented on TEZ-2307:
-
[~zjffdu] - not sure if this patch is ready for review yet or not. I was
looking at the code - and I think there's another problem around the way the
state transitions happen.
If a dag is accepted before the AM transitions all it's states - there's a
possibility that the DAG_FINISHED event and the subsequent DAG_CLEANUP have not
been processed. If DAG_CLEANUP is processed after a new DAG is submitted, we
may see additional errors with that DAG - since cleanup notifies components
about the previous dag finishing, and also empties the ID caches. This could
result in all kinds of strange errors with the newly submitted DAG. There's a
small chance that synchronization is taking care of this - but I have my
doubts, since 'submitDAG' holds the lock on the AppMaster - so just allowing a
new DAG to be submitted may guarantee out of order execution of the previous
DAGs cleanup - instead of throwing the exception that it throws today.
I think we need to make the new DAG submission wait till the previous DAG has
been cleaned up.
> Possible wrong error message when submitting new dag
>
>
> Key: TEZ-2307
> URL: https://issues.apache.org/jira/browse/TEZ-2307
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Attachments: TEZ-2307-1.patch
>
>
> In the following 2 cases, AM would propagate wrong error message to client
> ("App master already running a DAG")
> * The last dag is completed but AM is still in RUNNING state
> * AM is in shutting down.
> {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)
[jira] [Commented] (TEZ-391) SharedEdge - Support for passing same output from a vertex as input to two different vertices
[
https://issues.apache.org/jira/browse/TEZ-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15090040#comment-15090040
]
TezQA commented on TEZ-391:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12734397/TEZ-391-WIP-7.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1413//console
This message is automatically generated.
> SharedEdge - Support for passing same output from a vertex as input to two
> different vertices
> -
>
> Key: TEZ-391
> URL: https://issues.apache.org/jira/browse/TEZ-391
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Rohini Palaniswamy
>Assignee: Jeff Zhang
> Attachments: Shared Edge Design.pdf, TEZ-391-WIP-1.patch,
> TEZ-391-WIP-2.patch, TEZ-391-WIP-3.patch, TEZ-391-WIP-4.patch,
> TEZ-391-WIP-5.patch, TEZ-391-WIP-6.patch, TEZ-391-WIP-7.patch
>
>
> We need this for lot of usecases. For cases where multi-query is turned off
> and for optimizing unions. Currently those are BROADCAST or ONE-ONE edges and
> we write the output multiple times.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[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=15090041#comment-15090041
]
TezQA commented on TEZ-1019:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12697692/TEZ-1019-5.patch
against master revision 85637c6.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1414//console
This message is automatically generated.
> Re-factor routing of events to use common code path for normal and recovery
> flow.
> -
>
> Key: TEZ-1019
> URL: https://issues.apache.org/jira/browse/TEZ-1019
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Hitesh Shah
>Assignee: Jeff Zhang
> Attachments: TEZ-1019-2.patch, TEZ-1019-3.patch, TEZ-1019-4.patch,
> TEZ-1019-5.patch, Tez-1019.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: TEZ-2307 PreCommit Build #1409
Jira: https://issues.apache.org/jira/browse/TEZ-2307
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/1409/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3540 lines...]
[INFO] Build failures were ignored.
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781162/TEZ-2307-1.patch
against master revision d5c9649.
{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 3.0.1) 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.dag.history.ats.acls.TestATSHistoryWithACLs
The following test timeouts occurred in :
org.apache.tez.test.TestRecovery
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1409//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1409//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
d1e2e5805fe0680f7ab1998186a4893d8ee21d14 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###
## FAILED TESTS (if any)
##
1 tests failed.
FAILED:
org.apache.tez.dag.history.ats.acls.TestATSHistoryWithACLs.testMultipleDagNonSession
Error Message:
test timed out after 5 milliseconds
Stack Trace:
java.lang.Exception: test timed out after 5 milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.tez.dag.history.ats.acls.TestATSHistoryWithACLs.testMultipleDagNonSession(TestATSHistoryWithACLs.java:463)
[jira] [Commented] (TEZ-2307) Possible wrong error message when submitting new dag
[
https://issues.apache.org/jira/browse/TEZ-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089028#comment-15089028
]
TezQA commented on TEZ-2307:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781162/TEZ-2307-1.patch
against master revision d5c9649.
{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 3.0.1) 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.dag.history.ats.acls.TestATSHistoryWithACLs
The following test timeouts occurred in :
org.apache.tez.test.TestRecovery
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/1409//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1409//console
This message is automatically generated.
> Possible wrong error message when submitting new dag
>
>
> Key: TEZ-2307
> URL: https://issues.apache.org/jira/browse/TEZ-2307
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Jeff Zhang
>Assignee: Jeff Zhang
> Fix For: 0.7.1, 0.8.2
>
> Attachments: TEZ-2307-1.patch
>
>
> In the following 2 cases, AM would propagate wrong error message to client
> ("App master already running a DAG")
> * The last dag is completed but AM is still in RUNNING state
> * AM is in shutting down.
> {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)
[jira] [Commented] (TEZ-2129) Task and Attempt views should contain links to the logs
[ https://issues.apache.org/jira/browse/TEZ-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15089246#comment-15089246 ] Sreenath Somarajapuram commented on TEZ-2129: - Yup, the changes are just in the UI and failure looks unrelated. > Task and Attempt views should contain links to the logs > --- > > Key: TEZ-2129 > URL: https://issues.apache.org/jira/browse/TEZ-2129 > Project: Apache Tez > Issue Type: Improvement > Components: UI >Reporter: Kevin J. Price >Assignee: Jonathan Eagles >Priority: Minor > Attachments: TEZ-2129.1.patch, TEZ-2129.2.patch > > > Currently, the actual task or attempt view does not contain a link to get to > the container logs. That link exists on the list view page, but not the view > page for a specific task/attempt. There should be a direct link to the logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
