[
https://issues.apache.org/jira/browse/HBASE-11724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095835#comment-14095835
]
Matteo Bertozzi commented on HBASE-11724:
-----------------------------------------
{quote}As worded "A value of 0 or 1 indicate to use the same set of queues for
gets and scans." could be interpreted to mean that when I set the value to '0'
queues are shared, and when I set the value to '1' the queues are also
shared.{quote}
The interpretation is correct, both 0 and 1 means that you share the same
queues..
{quote}It seems like could set it to 42 to turn off the get/scan sharing. The
fact that it is a float ratio between 0 and 1 is important to note here.{quote}
You can do what ever you want.. but the fact that it says "share" it should
point you to the fact that is a float.
{quote}if I just look at the hbase-default.xml I don't know what to expect. I
want to you make it clear for the user in the in hbase-default.xml{quote}
Any help with the wording? to me "Used in conjunction with
hbase.ipc.server.callqueue.read.share will split the read call queues into
small-read and long-read queues" is already clear enough and after that there
is also explained the 0 - 1 corner case... so if you have something to add feel
free to post it.
{quote}I didn't see it in this patch and theese values get used in the
calculations of # of counts. As a user I could put values in like -1 or 42 and
not know it was silly.{quote}
Yeah, you can put 42 and it will be solved by "if ((numReadQueues -
numScanQueues) > 0)"
> 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)
