[
https://issues.apache.org/jira/browse/HBASE-22559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-22559:
------------------------------
Fix Version/s: 3.0.0-alpha-1
> [RPC] set guard against CALL_QUEUE_HANDLER_FACTOR_CONF_KEY
> ----------------------------------------------------------
>
> Key: HBASE-22559
> URL: https://issues.apache.org/jira/browse/HBASE-22559
> Project: HBase
> Issue Type: Bug
> Components: rpc
> Reporter: Reid Chan
> Assignee: Reid Chan
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 1.5.0, 2.3.0, 2.2.1, 1.4.11
>
> Attachments: HBASE-22559.master.001.patch
>
>
> CALL_QUEUE_HANDLER_FACTOR_CONF_KEY is
> {{hbase.ipc.server.callqueue.handler.factor}}, a float number, which is
> supposed between [0.0, 1.0].
> If it is greater than 1, for example, 2.0, the call queues and handlers will
> be expanded twice:
> {code}
> float callQueuesHandlersFactor =
> this.conf.getFloat(CALL_QUEUE_HANDLER_FACTOR_CONF_KEY, 0);
> this.numCallQueues = computeNumCallQueues(handlerCount,
> callQueuesHandlersFactor);
> this.handlerCount = Math.max(handlerCount, this.numCallQueues);
> protected int computeNumCallQueues(final int handlerCount, final float
> callQueuesHandlersFactor) {
> return Math.max(1, (int) Math.round(handlerCount *
> callQueuesHandlersFactor));
> }
> {code}
> We already have {{hbase.regionserver.handler.count}} set, what mentioned
> above looks tricky.
> The purpose of this conf is to control how many handlers can share one call
> queue, expanding the number of handlers (a kind of side-effects) is not
> included, from my understanding.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
