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

["Duo Zhang (Jira)" <ji...@apache.org>]

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

Duo Zhang updated HBASE-26448:
------------------------------
    Fix Version/s: 3.0.0-alpha-3
                       (was: HBASE-26233)

> 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
>             Fix For: 3.0.0-alpha-3
>
>
> 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)