[
https://issues.apache.org/jira/browse/HBASE-6908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385756#comment-17385756
]
Richard Marscher commented on HBASE-6908:
-----------------------------------------
Looks like it auto linked. I submitted a pull request proposal for a solution:
https://github.com/apache/hbase/pull/3522
> Pluggable Call BlockingQueue for HBaseServer
> --------------------------------------------
>
> Key: HBASE-6908
> URL: https://issues.apache.org/jira/browse/HBASE-6908
> Project: HBase
> Issue Type: New Feature
> Components: IPC/RPC
> Reporter: James Taylor
> Priority: Major
>
> Allow the BlockingQueue implementation class to be specified in the HBase
> config to enable different behavior than a FIFO queue. The use case we have
> is around fairness and starvation for big scans that are parallelized on the
> client. It's easy to fill up the HBase server Call BlockingQueue when
> processing a single parallelized scan, leadng other scans to time out.
> Instead, doing round robin processesing on a dequeue through a different
> BlockingQueue implementation will prevent this from occurring.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
