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

Liyin Tang reassigned HBASE-5776:
---------------------------------

    Assignee: binlijin  (was: Liyin Tang)
    
> HTableMultiplexer 
> ------------------
>
>                 Key: HBASE-5776
>                 URL: https://issues.apache.org/jira/browse/HBASE-5776
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Liyin Tang
>            Assignee: binlijin
>         Attachments: ASF.LICENSE.NOT.GRANTED--D2775.1.patch, 
> ASF.LICENSE.NOT.GRANTED--D2775.1.patch, 
> ASF.LICENSE.NOT.GRANTED--D2775.2.patch, 
> ASF.LICENSE.NOT.GRANTED--D2775.2.patch, 
> ASF.LICENSE.NOT.GRANTED--D2775.3.patch, 
> ASF.LICENSE.NOT.GRANTED--D2775.4.patch, 
> ASF.LICENSE.NOT.GRANTED--D2775.5.patch, HBASE-5776-trunk.patch, 
> HBASE-5776-trunk-V2.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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to