[ 
https://issues.apache.org/jira/browse/HIVE-13858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310790#comment-15310790
 ] 

Siddharth Seth commented on HIVE-13858:
---------------------------------------

The test failures are unrelated. This particular run took over 4 hours compared 
to other runs which take 2 hours. However, from the logs it looks like the mvn 
build started at 23:00, and the test run completed at 01:19 - which is a 2h20m 
and consistent with other runs. Looks to be a delay in the run actually 
starting.

Committing.

> LLAP: A preempted task can end up waiting on completeInitialization if some 
> part of the executing code suppressed the interrupt
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-13858
>                 URL: https://issues.apache.org/jira/browse/HIVE-13858
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>            Priority: Blocker
>              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
(v6.3.4#6332)

Reply via email to