hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liang Xie (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-11355) a couple of callQueue related improvements
Date Mon, 16 Jun 2014 02:55:02 GMT
Liang Xie created HBASE-11355:

             Summary: a couple of callQueue related improvements
                 Key: HBASE-11355
                 URL: https://issues.apache.org/jira/browse/HBASE-11355
             Project: HBase
          Issue Type: Improvement
          Components: IPC/RPC
    Affects Versions: 0.94.20, 0.99.0
            Reporter: Liang Xie
            Assignee: Liang Xie

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)"

This message was sent by Atlassian JIRA

View raw message