[ https://issues.apache.org/jira/browse/HBASE-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539410#comment-13539410 ]
ramkrishna.s.vasudevan commented on HBASE-5776: ----------------------------------------------- {code} queue = serverToBufferQueueMap.get(addr); if (queue == null) { // Create the queue for the new region server queue = addNewRegionServer(addr, htable); } {code} The above piece of code is in getBufferedQueue(). May be we can directly call addNewRegionServer() only. Also addNewRegionServer is also synchronized. > HTableMultiplexer > ------------------ > > Key: HBASE-5776 > URL: https://issues.apache.org/jira/browse/HBASE-5776 > Project: HBase > Issue Type: Improvement > Reporter: Liyin Tang > Assignee: binlijin > Fix For: 0.96.0 > > Attachments: 5776-trunk-V3.patch, 5776-trunk-V4.patch, > 5776-trunk-V5.patch, 5776-trunk-V6.patch, > 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