[
https://issues.apache.org/jira/browse/HBASE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095995#comment-14095995
]
Matteo Bertozzi commented on HBASE-11724:
-----------------------------------------
{quote}read.share = 1.0 scan.share = .5 Does this mean that writes are 0%, gets
are 50% and scans are 50%{quote}
almost, but since 0% writes does not make sense you have at least 1 write
queue...
{quote}read.share = .5 .scan.share = .5
Does this mean that writes are 0%, gets are 50% and scans are 50%?
Or, does this mean that writes are 50%, gets are 25% and scans are 25%?
{quote}
The second one.. isn't this clear enough? "will split the READ CALL QUEUES
into small-read and long-read queues".
You split reads and writes, and then you split the scans. otherwise will result
too complicate to understand
can you wordify what you want to see in the doc? I'm a bit stuck here
> Add to RWQueueRpcExecutor the ability to split get and scan handlers
> --------------------------------------------------------------------
>
> Key: HBASE-11724
> URL: https://issues.apache.org/jira/browse/HBASE-11724
> Project: HBase
> Issue Type: New Feature
> Components: IPC/RPC
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-11724-v0.patch
>
>
> RWQueueRpcExecutor has the devision between reads and writes requests, but we
> can split also small-reads and long-reads. This can be useful to force a
> deprioritization of scans on the RS.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
