[jira] [Commented] (TEZ-3823) expose AM location and application ID from TezClient
[ https://issues.apache.org/jira/browse/TEZ-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144460#comment-16144460 ] Siddharth Seth commented on TEZ-3823: - [~sershe] - this is prone to errors, especially in case of AM recovery where the AM could restart on some other node. Why does the hostname need to be exposed? > expose AM location and application ID from TezClient > > > Key: TEZ-3823 > URL: https://issues.apache.org/jira/browse/TEZ-3823 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: TEZ-3823.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Failed: TEZ-3823 PreCommit Build #2621
Jira: https://issues.apache.org/jira/browse/TEZ-3823
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2621/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4.63 KB...]
Going to apply patch with: /usr/bin/patch -p0
patching file tez-api/src/main/java/org/apache/tez/client/TezClient.java
==
==
Determining number of patched javac warnings.
==
==
/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests -Ptest-patch >
/home/jenkins/jenkins-slave/workspace/PreCommit-TEZ-Build/../patchprocess/patchJavacWarnings.txt
2>&1
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884135/TEZ-3823.patch
against master revision b04e7fc.
{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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2621//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
bfe2c2eed71db3fde6c4f794ecdb3d78a169483d logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
ERROR: Step ?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-3823) expose AM location and application ID from TezClient
[
https://issues.apache.org/jira/browse/TEZ-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144413#comment-16144413
]
TezQA commented on TEZ-3823:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884135/TEZ-3823.patch
against master revision b04e7fc.
{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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2621//console
This message is automatically generated.
> expose AM location and application ID from TezClient
>
>
> Key: TEZ-3823
> URL: https://issues.apache.org/jira/browse/TEZ-3823
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: TEZ-3823.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TEZ-3823) expose AM location and application ID from TezClient
[ https://issues.apache.org/jira/browse/TEZ-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated TEZ-3823: -- Attachment: TEZ-3823.patch [~sseth] can you take a look? Small patch > expose AM location and application ID from TezClient > > > Key: TEZ-3823 > URL: https://issues.apache.org/jira/browse/TEZ-3823 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Attachments: TEZ-3823.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TEZ-3823) expose AM location and application ID from TezClient
[ https://issues.apache.org/jira/browse/TEZ-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated TEZ-3823: -- Summary: expose AM location and application ID from TezClient (was: expose AM location from TezClient) > expose AM location and application ID from TezClient > > > Key: TEZ-3823 > URL: https://issues.apache.org/jira/browse/TEZ-3823 > Project: Apache Tez > Issue Type: Bug >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TEZ-3823) expose AM location from TezClient
Sergey Shelukhin created TEZ-3823: - Summary: expose AM location from TezClient Key: TEZ-3823 URL: https://issues.apache.org/jira/browse/TEZ-3823 Project: Apache Tez Issue Type: Bug Reporter: Sergey Shelukhin Assignee: Sergey Shelukhin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TEZ-3822) Default threshold for blacklisting a node is too high
Zhiyuan Yang created TEZ-3822: - Summary: Default threshold for blacklisting a node is too high Key: TEZ-3822 URL: https://issues.apache.org/jira/browse/TEZ-3822 Project: Apache Tez Issue Type: Bug Reporter: Zhiyuan Yang By default, a task will be failed if 4 task attempts fail, which consequently fail the vertex and dag. By default, a node will be blacklisted if 10 task attempts fail on it. This number is higher than 4, so a single faulty node server can fail 4 task attempts by shuffle error, which finally fail the job, before this node is blacklisted. Even we can reschedule a task after it's blamed for input read error, we cannot avoid multiple tasks go to the same bad node and continue to cause shuffle error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
