hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-3673) Reduce HTable Pool Contention Using Concurrent Collections
Date Thu, 24 Mar 2011 22:30:06 GMT

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

stack updated HBASE-3673:

       Resolution: Fixed
    Fix Version/s:     (was: 0.90.0)
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

Committed to TRUNK.  Thanks for the patch Karthick.

> 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.92.0
>         Attachments: HBASE-3673-TESTCASE.patch, 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

View raw message