You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Varun Sharma (JIRA)" <ji...@apache.org> on 2012/12/07 01:05:20 UTC

[jira] [Created] (HBASE-7295) Contention in HBaseClient.getConnection

Varun Sharma created HBASE-7295:
-----------------------------------

             Summary: 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


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