[
https://issues.apache.org/jira/browse/HBASE-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack updated HBASE-9467:
---------------------------------
Comment: was deleted
(was: The lists all Apache HBase Jiras included in CDH 5 that are not included
in the Apache HBase base version 0.95.2. The
hbase-0.95.2-cdh5.0.0-beta-1.CHANGES.txt file lists all changes included in CDH
5. The patch for each change can be found in the cloudera/patches directory in
the release tarball.
HBASE-9735 - region_mover.rb uses the removed HConnection.getZooKeeperWatcher()
method
HBASE-9602 - Cluster can't start when log splitting at startup time and the
master's web UI is refreshed a few times
HBASE-9609 - AsyncProcess doesn't increase all the counters when trying to
limit the per region flow.
HBASE-9663 - PerformanceEvaluation does not properly honor specified table
name parameter
HBASE-9610 - TestThriftServer.testAll failing
HBASE-8711 - Requests count is completely off
HBASE-9653 - Add compaction metrics to trunk
HBASE-9650 - Per region metrics are not showing up for system tables.
HBASE-9600 - TestColumnSchemaModel and TestTableSchemaModel test cases are
failing with IBM IBM Java 6
HBASE-9603 - IsRestoreSnapshotDoneResponse has wrong default causing
restoreSnapshot() to be async
HBASE-9597 - Create hbase-thrift module
HBASE-9558 - PerformanceEvaluation is in hbase-server, and create a dependency
to MiniDFSCluster
HBASE-9585 - Update javadoc builder in pom to exclude empty packages in user
api javadoc
HBASE-9579 - Sanity check visiblity and audience for server-side modules.
HBASE-9533 - List of dependency jars for MR jobs is hard-coded and does not
include netty, breaking MRv1 jobs
HBASE-9586 - Deprecate remove o.a.h.h.util.Keying class.
HBASE-9581 - Few tests broken since HBASE-9551
John William
[https://www.freeessaywriter.net/])
> 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: Honghua Feng
> Assignee: Honghua Feng
> Priority: Major
> 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 was sent by Atlassian Jira
(v8.3.4#803005)
