[
https://issues.apache.org/jira/browse/TEZ-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649466#comment-15649466
]
TezQA commented on TEZ-3533:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12838085/TEZ-3533.1.patch
against master revision eb6fb67.
{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.client.TestTezClient
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2097//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2097//console
This message is automatically generated.
> ShuffleScheduler should shutdown threadpool on exit
> ---------------------------------------------------
>
> Key: TEZ-3533
> URL: https://issues.apache.org/jira/browse/TEZ-3533
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Priority: Critical
> Attachments: TEZ-3533.1.patch
>
>
> In normal tez executions this wouldn't be a problem. But in environments like
> LLAP, this could be a potential issue and end up with large number of fetcher
> threads idling in the JVM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
