Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 7 Dec 2012 00:07:20 +0000 (UTC)
From: "Varun Sharma (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12622834.1354838627555.643.1354838840528@arcas>
In-Reply-To: <JIRA.12622834.1354838627555@arcas>
References: <JIRA.12622834.1354838627555@arcas>
Subject: [jira] [Updated] (HBASE-7295) Contention in
 HBaseClient.getConnection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-7295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Sharma updated HBASE-7295:
--------------------------------

    Attachment: 7295-0.94.txt
    
> 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
>         Attachments: 7295-0.94.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