[
https://issues.apache.org/jira/browse/HIVE-16655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009986#comment-16009986
]
Hive QA commented on HIVE-16655:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12867903/HIVE-16655.02.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 10699 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/5257/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/5257/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-5257/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12867903 - PreCommit-HIVE-Build
> LLAP: Avoid preempting fragments before they enter the running state
> --------------------------------------------------------------------
>
> Key: HIVE-16655
> URL: https://issues.apache.org/jira/browse/HIVE-16655
> Project: Hive
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-16655.01.patch, HIVE-16655.02.patch
>
>
> Currently in the AM, fragments may be preempted as soon as they are
> allocated, without knowing whether they will move into the RUNNING state or
> not. Leads to a lot of unnecessary kills.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
