[
https://issues.apache.org/jira/browse/HBASE-22418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841472#comment-16841472
]
Biju Nair commented on HBASE-22418:
---
Summary of the proposed change. Currently {{SimpleRpcScheduler}} uses
[RWQueueRpcExecutor|https://github.com/apache/hbase/blob/e984515b7426e8df9e0e50abc6a998f23d5e6e9e/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/SimpleRpcScheduler.java#L91]
when {{hbase.ipc.server.callqueue.read.ratio}} property is set to a value > 0.
{{RWQueueRpcExecutor}} splits the queues and handlers for {{read}} and
{{write}} requests. It also provides the option to split the {{read}}
queue/handlers further to handle {{get}} and {{scan}} requests by setting the
{{hbase.ipc.server.callqueue.scan.ratio}} property. The proposed change is to
add a new property {{hbase.ipc.server.callqueue.multiread.ratio}} which the
users can set to define the percentage of the {{read}} queue/handlers to serve
Multi get/batch requests. This will let users to define separate {{read}}
queue/handlers for {{get}}, {{scan}}, {{multi get/batch get}} requests.
> Separate queue/executor for Multi get requests
> --
>
> Key: HBASE-22418
> URL: https://issues.apache.org/jira/browse/HBASE-22418
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
>Reporter: Biju Nair
>Priority: Major
> Attachments: HBASE-22418.DRAFT
>
>
> Using {{RWQueueRpcExecutor}}, {{SimpleRpcScheduler}} lets us define separate
> queue/handlers to process write, read and scan requests. If this can be
> extended to have separate queue/handlers for multi get requests, it will help
> processing single get requests quickly where there is a mix of multi and
> single get workload. This is the case for multi put/single put as well. Any
> drawbacks in doing this segregation?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
