Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 14 Dec 2015 23:55:46 +0000 (UTC)
From: "Prasanth Jayachandran (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12860437.1440800192000.20604.1450137346622@Atlassian.JIRA>
In-Reply-To: <JIRA.12860437.1440800192000@Atlassian.JIRA>
References: <JIRA.12860437.1440800192000@Atlassian.JIRA>
 <JIRA.12860437.1440800192923@arcas>
Subject: [jira] [Assigned] (HIVE-11687) TaskExecutorService can reject work
 even if capacity is available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanth Jayachandran reassigned HIVE-11687:
--------------------------------------------

    Assignee: Prasanth Jayachandran

> 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)