Geoffrey Jacoby created PHOENIX-5482:
----------------------------------------
Summary: PhoenixRpcScheduler should use HBase priority max queue
length
Key: PHOENIX-5482
URL: https://issues.apache.org/jira/browse/PHOENIX-5482
Project: Phoenix
Issue Type: Improvement
Reporter: Geoffrey Jacoby
HBase 1.3 and 2.0 introduced the hbase.ipc.server.priority.max.callqueue.length
setting in HBASE-15470, to allow operators to vary the max queue length size
for hbase:meta requests independently of normal regions.
The PhoenixRpcScheduler doesn't check this setting, and uses the existing
hbase.ipc.server.max.callqueue.length for all of its queues (normal, index, and
metadata). While we should still default to this setting if the newer priority
callqueue setting isn't present, Phoenix should use the new setting for index
and metadata queues if it's present.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
