You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Zheng Wang (Jira)" <ji...@apache.org> on 2021/03/07 07:58:00 UTC

[jira] [Updated] (HBASE-25643) The delayed FlushRegionEntry should be removed when we need a non-delayed one

     [ https://issues.apache.org/jira/browse/HBASE-25643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zheng Wang updated HBASE-25643:
-------------------------------
    Attachment:     (was: image-2021-03-07-15-34-26-597.png)

> The delayed FlushRegionEntry should be removed when we need a non-delayed one
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-25643
>                 URL: https://issues.apache.org/jira/browse/HBASE-25643
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>            Reporter: Zheng Wang
>            Assignee: Zheng Wang
>            Priority: Major
>
> The regionserver periodically check all the regions, if one not flushed for long time, then it will create a delayed FlushRegionEntry, the delay range is 0~300.
> During the delay time, if many data are written to the region suddenly, we can not do the flush immediately due to the existing one in regionsInQueue, then the RegionTooBusyException will occur.
> It is better to improve the logic here, that the delayed entry should be replaced by the non-delayed one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)