You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2021/11/14 13:05:00 UTC

[jira] [Assigned] (HBASE-26448) Make sure we do not flush a region too frequently

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

Duo Zhang reassigned HBASE-26448:
---------------------------------

    Assignee: Duo Zhang

> Make sure we do not flush a region too frequently
> -------------------------------------------------
>
>                 Key: HBASE-26448
>                 URL: https://issues.apache.org/jira/browse/HBASE-26448
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>
> In HBASE-26412, once we found there is an error replicating the edits, we will trigger a flush, and in HBASE-26413, we are likely to also trigger a flush when the pending edits are too large.
> We should find a way to avoid flushing the region too much.
> And a failure of replicating usually means the region is moved or the target region server is crashed, only a flush after the secondary replica is online will be useful, so flushing the region lots of times before the scedondary replica online is just useless.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)