[HBASE-11355] a couple of callQueue related improvements

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.99.0, 0.94.20
• Fix Version/s: 0.99.0, 0.98.4
• Component/s: IPC/RPC, Performance, Scheduler
• Release Note: Near double the random read throughput (On random test bench with 8 clients running ycsb workloadc against a single server, see throughput go from 180k to 335k ops a second).
• Assignee: Matteo Bertozzi
• Reporter: Liang Xie
• Created: 16/Jun/14 02:54
• Updated: 16/May/19 20:33
• Resolved: 01/Jul/14 08:38

Description

In one of my in-memory read only testing(100% get requests), one of the top scalibility bottleneck came from the single callQueue. A tentative sharing this callQueue according to the rpc handler number showed a big throughput improvement(the original get() qps is around 60k, after this one and other hotspot tunning, i got 220k get() qps in the same single region server) in a YCSB read only scenario.
Another stuff we can do is seperating the queue into read call queue and write call queue, we had done it in our internal branch, it would helpful in some outages, to avoid all read or all write requests ran out of all handler threads.
One more stuff is changing the current blocking behevior once the callQueue is full, considering the full callQueue almost means the backend processing is slow somehow, so a fail-fast here should be more reasonable if we using HBase as a low latency processing system. see "callQueue.put(call)"

Issue Links

• is related to: PHOENIX-938 Use higher priority queue for index updates to prevent deadlock
• relates to: HBASE-10994 HBase Multi-Tenancy

Sub-Tasks

• Document callQueue improvements from HBASE-11355 and HBASE-11724: Closed