hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16104) LLAP: preemption may be too aggressive if the pre-empted task doesn't die immediately
Date Fri, 10 Mar 2017 03:42:38 GMT

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

Siddharth Seth commented on HIVE-16104:
---------------------------------------

bq. Sorry didn't get that. You mean for the waiting for completion? Wouldn't that block other
ops like adding tasks?
No. It's a wait on the giant lock. So there's no lock held. When a new operation happens,
it can signal this. (The same lock used in the main scheduling loop) - which gets a signal
from all other opeartions.

Also, I think the loop can be simplified. trySChedule does not need to be done twice.


> LLAP: preemption may be too aggressive if the pre-empted task doesn't die immediately
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-16104
>                 URL: https://issues.apache.org/jira/browse/HIVE-16104
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-16104.01.patch, HIVE-16104.02.patch, HIVE-16104.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message