[ https://issues.apache.org/jira/browse/HBASE-9467 ]
shreedurgapg deleted comment on HBASE-9467:
-------------------------------------
was (Author: JIRAUSER283692):
Thanks..
[pg accomodation in gurgaon sector 49|https://shreedurgapg.com/]
[pg in sector 33 gurgaon|https://shreedurgapg.com/]
[pg accomodation in gurgaon sector 48|https://shreedurgapg.com/]
[boys pg in sector 49 gurgaon|https://shreedurgapg.com/]
> 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.20.1#820001)
