You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Karthick Sankarachary (JIRA)" <ji...@apache.org> on 2011/03/18 23:31:29 UTC
[jira] Updated: (HBASE-3673) Reduce HTable Pool Contention Using
Concurrent Collections
[ https://issues.apache.org/jira/browse/HBASE-3673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthick Sankarachary updated HBASE-3673:
-----------------------------------------
Status: Patch Available (was: Open)
> Reduce HTable Pool Contention Using Concurrent Collections
> ----------------------------------------------------------
>
> Key: HBASE-3673
> URL: https://issues.apache.org/jira/browse/HBASE-3673
> Project: HBase
> Issue Type: Improvement
> Components: client
> Affects Versions: 0.90.1, 0.90.2
> Reporter: Karthick Sankarachary
> Assignee: Karthick Sankarachary
> Priority: Minor
> Fix For: 0.90.0
>
> Attachments: HBASE-3673.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> In the case of medium-to-large sized HTable pools, the amount of time the client spends blocking on the underlying map and queue data structures turns out to be quite significant. Using an efficient wait-free implementation of maps and queues might serve to reduce the contention on the pool. In particular, I was wondering if we should replace the synchronized map with a concurrent hash map, and linked list with a concurrent linked queue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira