[
https://issues.apache.org/jira/browse/TEZ-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169260#comment-15169260
]
TezQA commented on TEZ-3128:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12790142/TEZ-3128.004.patch
against master revision 15d7339.
{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:red}-1 javac{color}. The applied patch generated 31 javac
compiler warnings (more than the master's current 30 warnings).
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 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/1518//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1518//artifact/patchprocess/newPatchFindbugsWarningstez-runtime-library.html
Javac warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/1518//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/1518//console
This message is automatically generated.
> Avoid stopping containers on the AM shutdown thread
> ---------------------------------------------------
>
> Key: TEZ-3128
> URL: https://issues.apache.org/jira/browse/TEZ-3128
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.8.0-alpha
> Reporter: Siddharth Seth
> Assignee: Tsuyoshi Ozawa
> Labels: newbie
> Attachments: TEZ-3128.001.patch, TEZ-3128.002.patch,
> TEZ-3128.003.patch, TEZ-3128.004.patch, amJstack
>
>
> During an AM shutdown, the TaskCommunicator is also shutdown and it tries to
> stop containers in the shutdown thread itself. This can cause the AM shutdown
> to block if NMs are not available.
> This likely affects 0.7 as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
