hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ming Ma (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HADOOP-13029) Have FairCallQueue try all lower priority sub queues before backoff
Date Fri, 15 Apr 2016 23:53:25 GMT
Ming Ma created HADOOP-13029:
--------------------------------

             Summary: Have FairCallQueue try all lower priority sub queues before backoff
                 Key: HADOOP-13029
                 URL: https://issues.apache.org/jira/browse/HADOOP-13029
             Project: Hadoop Common
          Issue Type: Sub-task
            Reporter: Ming Ma


Currently if FairCallQueue and backoff are enabled, backoff will kick in as soon as the assigned
sub queue is filled up.

{noformat}
  /**
   * Put and offer follow the same pattern:
   * 1. Get the assigned priorityLevel from the call by scheduler
   * 2. Get the nth sub-queue matching this priorityLevel
   * 3. delegate the call to this sub-queue.
   *
   * But differ in how they handle overflow:
   * - Put will move on to the next queue until it lands on the last queue
   * - Offer does not attempt other queues on overflow
   */
{noformat}

Seems it is better to try lower priority sub queues when the assigned sub queue is full, just
like the case when backoff is disabled. This will give regular users more opportunities and
allow the cluster to be configured with smaller call queue length. [~chrili], [~arpitagarwal],
what do you think?



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

Mime
View raw message