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-11687) TaskExecutorService can reject work even if capacity is available
Date Wed, 16 Dec 2015 01:13:46 GMT

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

Siddharth Seth commented on HIVE-11687:
---------------------------------------

[~prasanth_j] - I don't think I ever saw this. However, this scenario is possible - typically
in case of high contention on available resources. Notifying the executor does nit mean it
will start running (and acquire the lock) immediately. Instead another submission could come
in - take the lock - find the wait queue to be full and be rejected.

> TaskExecutorService can reject work even if capacity is available
> -----------------------------------------------------------------
>
>                 Key: HIVE-11687
>                 URL: https://issues.apache.org/jira/browse/HIVE-11687
>             Project: Hive
>          Issue Type: Sub-task
>          Components: llap
>    Affects Versions: llap
>            Reporter: Siddharth Seth
>            Assignee: Prasanth Jayachandran
>             Fix For: llap
>
>
> The waitQueue has a fixed capacity - which is the wait queue size. Addition of new work
doe snot factor in the capacity available to execute work. This ends up being left to the
race between work getting scheduled for execution and added to the waitQueue.
> cc [~prasanth_j]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message