hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-13858) LLAP: A preempted task can end up waiting on completeInitialization if some part of the executing code suppressed the interrupt
Date Wed, 01 Jun 2016 01:18:12 GMT


Hive QA commented on HIVE-13858:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 12 failed/errored test(s), 10195 tests executed
*Failed tests:*
TestHWISessionManager - did not produce a TEST-*.xml file
TestJdbcWithMiniHA - did not produce a TEST-*.xml file
TestJdbcWithMiniMr - did not produce a TEST-*.xml file
TestOperationLoggingAPIWithTez - did not produce a TEST-*.xml file

Test results:
Console output:
Test logs:

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
Tests exited with: TestsFailedException: 12 tests failed

This message is automatically generated.

ATTACHMENT ID: 12806662 - PreCommit-HIVE-MASTER-Build

> LLAP: A preempted task can end up waiting on completeInitialization if some part of the
executing code suppressed the interrupt
> -------------------------------------------------------------------------------------------------------------------------------
>                 Key: HIVE-13858
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Critical
>              Labels: llap
>         Attachments: HIVE-13858.01.patch, HIVE-13858.02.patch, HIVE-13858.03.patch
> An interrupt along with a HiveProcessor.abort call is made when attempting to preempt
a task.
> In this specific case, the task was in the middle of HDFS IO - which 'handled' the interrupt
by retrying. As a result the interrupt status on the thread was reset - so instead of skipping
the future.get in completeInitialization - the task ended up blocking there.
> End result - a single executor slot permanently blocked in LLAP. Depending on what else
is running - this can cause a cluster level deadlock.

This message was sent by Atlassian JIRA

View raw message