[
https://issues.apache.org/jira/browse/HBASE-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244403#comment-17244403
]
esther sherryworld commented on HBASE-9467:
-------------------------------------------
* [HBASE-9314] - Dropping a table always prints a TableInfoMissingException in
the master log
* [HBASE-9438] - Enhance hbase shell un/assign to take encoded region name
* [HBASE-9373] - [replication] data loss because replication doesn't expect
partial reads
* [HBASE-9385] - Log HBase Master command line arguments on startup
* [HBASE-9208] - ReplicationLogCleaner slow at large scale
* [HBASE-9371] - Eliminate log spam when tailing files
* [HBASE-9330] - Refactor PE to create HTable the correct way
* [HBASE-9313] - NamespaceJanitor is spammy when the namespace table moves
* [HBASE-9116] - Add a view/edit tool for favored node mappings for regions
* [HBASE-9248] - Place holders for tags in 0.96 to accommodate tags in 0.98
* [HBASE-8754] - Log the client IP/port of the balancer invoker
* [HBASE-8441] - [replication] Refactor KeeperExceptions thrown from
replication state interfaces into replication specific exceptions
* [HBASE-9273] - Consolidate isSystemTable checking
* [HBASE-9243] - Add more useful statistics in the HFile tool
Esther Sherry
[https://sites.google.com/site/bestessaywritingservicereview/|https://sites.google.com/site/bestessaywritingservicereview/]
> 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)
