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

Hudson commented on HADOOP-10279:
---------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #5742 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/5742/])
HADOOP-10279. Create multiplexer, a requirement for the fair queue. 
(Contributed by Chris Li) (arp: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1604090)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/WeightedRoundRobinMultiplexer.java
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestWeightedRoundRobinMultiplexer.java


> Create multiplexer, a requirement for the fair queue
> ----------------------------------------------------
>
>                 Key: HADOOP-10279
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10279
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Chris Li
>            Assignee: Chris Li
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: HADOOP-10279.patch, HADOOP-10279.patch, 
> WeightedRoundRobinMultiplexer.java, subtask2_add_mux.patch
>
>
> The Multiplexer helps the FairCallQueue decide which of its internal 
> sub-queues to read from during a poll() or take(). It controls the penalty of 
> being in a lower queue. Without the mux, the FairCallQueue would have issues 
> with starvation of low-priority requests.
> The WeightedRoundRobinMultiplexer is an implementation which uses a weighted 
> round robin approach to muxing the sub-queues. It is configured with an 
> integer list pattern.
> For example: 10, 5, 5, 2 means:
> * Read queue 0 10 times
> * Read queue 1 5 times
> * Read queue 2 5 times
> * Read queue 3 2 times
> * Repeat



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to