[
https://issues.apache.org/jira/browse/TEZ-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312199#comment-16312199
]
TezQA commented on TEZ-3880:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12904680/TEZ-3880.patch
against master revision 4c378b4.
{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.tests.TestExternalTezServices
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2707//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2707//console
This message is automatically generated.
> do not count rejected tasks as killed in vertex progress
> --------------------------------------------------------
>
> Key: TEZ-3880
> URL: https://issues.apache.org/jira/browse/TEZ-3880
> Project: Apache Tez
> Issue Type: Task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: TEZ-3880.patch
>
>
> Tasks rejected from LLAP because the cluster is full are shown as killed
> tasks in the commandline query UI (CLI and beeline). This shouldn't really
> happen; killed tasks in the container case means something else, and this
> scenario doesn't exist because AM doesn't continuously try to queue tasks. We
> could change LLAP queue to use sort of a pull model (would also allow for
> better duplicate scheduling), but for now we should fix the UI
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
