[
https://issues.apache.org/jira/browse/HADOOP-14032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859751#comment-15859751
]
Hudson commented on HADOOP-14032:
---------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11225 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/11225/])
HADOOP-14032. Reduce fair call queue priority inversion. Contributed by
(kihwal: rev a0bfb4150464013a618f30c2e38d88fc6de11ad2)
* (edit)
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestFairCallQueue.java
* (edit)
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/FairCallQueue.java
> Reduce fair call queue priority inversion
> -----------------------------------------
>
> Key: HADOOP-14032
> URL: https://issues.apache.org/jira/browse/HADOOP-14032
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ipc
> Affects Versions: 2.7.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 2.8.1, 3.0.0-alpha3
>
> Attachments: HADOOP-14032.patch
>
>
> The fcq's round robin multiplexer actually rewards abusive users. Queue
> consumers scan for a call from the roving multiplexer index to the lowest
> prio ring before wrapping around to the higher prio rings.
> Let's take a fcq with 4 priority rings. Multiplexer shares per index are 8,
> 4, 2, 1.
> All well behaved clients are operating in ring 0. Bad client floods the
> server and drops to the lowest prio. Unfortunately the service order gives 8
> shares to the good clients, followed by 4+2+1=7 shares to the bad client.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
