[
https://issues.apache.org/jira/browse/HBASE-11737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14102952#comment-14102952
]
Matteo Bertozzi commented on HBASE-11737:
-----------------------------------------
{quote}
hbase.ipc.server.callqueue.read.ratio
This factor weights the queues toward reads (if below .5) or writes (if above
.5).
{quote}
Other way around, the examples are ok except one.
{quote}
A value of .6 uses 75% of the queues for writing and 25% for reading. Given a
value of 10 for
hbase.ipc.server.num.callqueue, 7 queues would be used for reads and 3 for
writes.</para>
{quote}
some weird math in here. 0.6 should give you 60% and not 75% it is basically
the reverse of the 0.3 example above which is good. and it is also 60% of
reading (only the first part is wrong)
{quote}
You can also split the read queues so that separate queues are used for short
reads
(from Get operations) and short reads (from Scan operations)
{quote}
short read (get) and long reads (scan) you have two "short" in there.
> Document callQueue improvements from HBASE-11355 and HBASE-11724
> ----------------------------------------------------------------
>
> Key: HBASE-11737
> URL: https://issues.apache.org/jira/browse/HBASE-11737
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Fix For: 0.99.0, 0.98.4
>
> Attachments: HBASE-11737.patch, HBASE-11737.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
