[
https://issues.apache.org/jira/browse/HADOOP-13029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Krogen updated HADOOP-13029:
---------------------------------
Issue Type: Improvement (was: Sub-task)
Parent: (was: HADOOP-9640)
> 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: Improvement
> Components: ipc
> Reporter: Ming Ma
> Priority: Major
> Labels: qos, rpc
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
