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

Posted to issues@hbase.apache.org by "Xiaolin Ha (Jira)" <ji...@apache.org> on 2021/12/07 04:32:00 UTC

[jira] [Resolved] (HBASE-26526) Introduce a timeout to shutdown of WAL

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

Xiaolin Ha resolved HBASE-26526.
--------------------------------
    Fix Version/s: 3.0.0-alpha-2
       Resolution: Fixed

Merged to branch master, thanks [~apurtell]  for reviewing.

> Introduce a timeout to shutdown of WAL
> --------------------------------------
>
>                 Key: HBASE-26526
>                 URL: https://issues.apache.org/jira/browse/HBASE-26526
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>    Affects Versions: 3.0.0-alpha-1, 2.0.0
>            Reporter: Xiaolin Ha
>            Assignee: Xiaolin Ha
>            Priority: Major
>             Fix For: 3.0.0-alpha-2
>
>
> When the regionserver is aborted(server.isAborted() is true), it will just reject the newly coming requests, so it is important to keep a short time to stop to make a short MTTR. 
> When the WAL is shutting down, we can wait some time to flush the unacked appends, but if that is a long time, I think we can just abort without flushing them. 
> By introducing a timeout for WAL shutdown, we can control the shutdown time, especially for those sensitive businesses.



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