[
https://issues.apache.org/jira/browse/TEZ-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482525#comment-14482525
]
Hadoop QA commented on TEZ-2269:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12723522/TEZ-2269.altlock.txt
against master revision b87a36f.
{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/404//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/404//console
This message is automatically generated.
> DAGAppMaster becomes unresponsive
> ---------------------------------
>
> Key: TEZ-2269
> URL: https://issues.apache.org/jira/browse/TEZ-2269
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Rajesh Balamohan
> Attachments: TEZ-2269.altlock.txt, TEZ-2269.altlock.txt,
> TEZ-2269.test.patch, app_master_application_1428021179455_0001_jstack.txt,
> client_jstack.txt
>
>
> Scenario:
> - Run TPCH query20 @ 1 TB scale
> - Tez master branch, Hive trunk
> - auto-reduce parallelism is not an issue (happens with/without auto-reduce
> parallelism)
> 1 or 2 times in 10 runs, DAGAppMaster would freeze unexpectedly. There is no
> pattern observed on which vertex it happens. But when this happens, only
> option is to kill the application. I will attach the jstack soon, but that
> doesn't seem to reveal much.
> Need to debug more; Creating this JIRA for tracking purposes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
