[
https://issues.apache.org/jira/browse/HBASE-7295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602025#comment-13602025
]
Varun Sharma commented on HBASE-7295:
-------------------------------------
I would like to revive this issue. We have been running with this patch for
over a month now. Just to recap on the patch, we had contention issues at one
of our thrift proxy(s). The proxy does the following:
python client(s) <-> Thrift Proxy <-> HBase
The Proxy upto thousands of calls per second. However there are certain calls
which result in multi operations - these operations generate 30 calls for every
single call (which are upto 200-300 per second) - so basically this requires
locking the pool of connections, thousands of times per second - once for each
fanout call.
I have not rerun the tests yet against the most current 0.94 release but I
would like to pull it back into 0.94 (since we have tested it in production for
a while now).
Varun
> Contention in HBaseClient.getConnection
> ---------------------------------------
>
> Key: HBASE-7295
> URL: https://issues.apache.org/jira/browse/HBASE-7295
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.94.3
> Reporter: Varun Sharma
> Assignee: Varun Sharma
> Fix For: 0.95.0
>
> Attachments: 7295-0.94.txt, 7295-0.94-v2.txt, 7295-0.94-v3.txt,
> 7295-0.94-v4.txt, 7295-0.94-v5.txt, 7295-trunk.txt, 7295-trunk.txt,
> 7295-trunk-v2.txt, 7295-trunk-v3.txt, 7295-trunk-v3.txt
>
>
> HBaseClient.getConnection() synchronizes on the connections object. We found
> severe contention on a thrift gateway which was fanning out roughly 3000+
> calls per second to hbase region servers. The thrift gateway had 2000+
> threads for handling incoming connections. Threads were blocked on the
> syncrhonized block - we set ipc.pool.size to 200. Since we are using
> RoundRobin/ThreadLocal pool only - its not necessary to synchronize on
> connections - it might lead to cases where we might go slightly over the
> ipc.max.pool.size() but the additional connections would timeout after
> maxIdleTime - underlying PoolMap connections object is thread safe.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
