hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5776) HTableMultiplexer
Date Fri, 13 Apr 2012 21:37:22 GMT

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

Phabricator updated HBASE-5776:
-------------------------------

    Attachment: D2775.2.patch

Liyin updated the revision "[jira][89-fb][HBASE-5776] HTableMultiplexer".
Reviewers: Kannan

  As discussed with Kannan offline, HTableMultiplexer will keep a pool htable instance. So
user doesn't need to pass the htable as parameter for the put request. Also keep each put
retrying several times before failing and clear the cache location after failing.

  Add more java doc and license.

REVISION DETAIL
  https://reviews.facebook.net/D2775

AFFECTED FILES
  src/main/java/org/apache/hadoop/hbase/HConstants.java
  src/main/java/org/apache/hadoop/hbase/client/HConnection.java
  src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
  src/main/java/org/apache/hadoop/hbase/client/HTable.java
  src/main/java/org/apache/hadoop/hbase/client/HTableMultiplexer.java
  src/main/java/org/apache/hadoop/hbase/client/MultiPut.java
  src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
  src/test/java/org/apache/hadoop/hbase/client/TestHTableMultiplexer.java

                
> HTableMultiplexer 
> ------------------
>
>                 Key: HBASE-5776
>                 URL: https://issues.apache.org/jira/browse/HBASE-5776
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>         Attachments: D2775.1.patch, D2775.1.patch, D2775.2.patch, D2775.2.patch
>
>
> There is a known issue in HBase client that single slow/dead region server could slow
down the multiput operations across all the region servers. So the HBase client will be as
slow as the slowest region server in the cluster. 
>  
> To solve this problem, HTableMultiplexer will separate the multiput submitting threads
with the flush threads, which means the multiput operation will be a nonblocking operation.

> The submitting thread will shard all the puts into different queues based on its destination
region server and return immediately. The flush threads will flush these puts from each queue
to its destination region server. 
> Currently the HTableMultiplexer only supports the put operation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message