[
https://issues.apache.org/jira/browse/HIVE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058841#comment-15058841
]
Prasanth Jayachandran commented on HIVE-11687:
----------------------------------------------
[~sseth] Are you still seeing this issue recently? WaitQueueThread will get
notified as soon a new element is added to the wait queue. Executor threads get
filled up as new works arrives in wait queue. My guess is notification is sent
out late (probably because of kill of evicted task, state update etc.) during
wait queue gets filled up and starts rejected. I think we should pull the
notification up in the schedule() method before killing the evicted task inside
the same synchronization block. Thoughts?
> 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)
