[jira] [Commented] (HIVE-11687) TaskExecutorService can reject work even if capacity is available

["Siddharth Seth (JIRA)" <ji...@apache.org>]

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

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

The patch essentially makes the waitQueue accept additional fragments if other fragments are about to complete, or have not yet been scheduled (total allowed capacity = executors + wait queue).
Given that other threads are in the process of terminating, we could setup additional threads to start processing the new work.

> 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
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-11687.WIP.txt
>
>
> 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.15#6346)