[ https://issues.apache.org/jira/browse/HBASE-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769213#comment-13769213 ]
Hudson commented on HBASE-9467: ------------------------------- SUCCESS: Integrated in HBase-TRUNK #4519 (See [https://builds.apache.org/job/HBase-TRUNK/4519/]) HBASE-9467 write can be totally blocked temporarily by a write-heavy region (stack: rev 1523881) * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java > write can be totally blocked temporarily by a write-heavy region > ---------------------------------------------------------------- > > Key: HBASE-9467 > URL: https://issues.apache.org/jira/browse/HBASE-9467 > Project: HBase > Issue Type: Improvement > Reporter: Feng Honghua > Assignee: Feng Honghua > Fix For: 0.98.0, 0.96.0 > > Attachments: HBASE-9467-trunk-v0.patch, HBASE-9467-trunk-v1.patch, > HBASE-9467-trunk-v1.patch, HBASE-9467-trunk-v1.patch > > > Write to a region can be blocked temporarily if the memstore of that region > reaches the threshold(hbase.hregion.memstore.block.multiplier * > hbase.hregion.flush.size) until the memstore of that region is flushed. > For a write-heavy region, if its write requests saturates all the handler > threads of that RS when write blocking for that region occurs, requests of > other regions/tables to that RS also can't be served due to no available > handler threads...until the pending writes of that write-heavy region are > served after the flush is done. Hence during this time period, from the RS > perspective it can't serve any request from any table/region just due to a > single write-heavy region. > This sounds not very reasonable, right? Maybe write requests from a region > can only be served by a sub-set of the handler threads, and then write > blocking of any single region can't lead to the scenario mentioned above? > Comment? -- 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