You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Michael Stack (Jira)" <ji...@apache.org> on 2020/07/23 04:01:00 UTC

[jira] [Comment Edited] (HBASE-24632) Enable procedure-based log splitting as default in hbase3

    [ https://issues.apache.org/jira/browse/HBASE-24632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163200#comment-17163200 ] 

Michael Stack edited comment on HBASE-24632 at 7/23/20, 4:00 AM:
-----------------------------------------------------------------

I was going to push this as default in hbase-2.4 and on hbase3 in the morning unless objections. I've been running it a while and its nice... There is a procedure per WAL split and ServerCrashProcedure doesn't block and wait till ALL WALs split before it can move forward; now it schedules all the WAL splits and then suspends itself freeing up the ProcedureExecutor to do other work.


was (Author: stack):
I was going to push this as default in hbase-2.4 and on hbase3 in the morning unless objections. I've been running it a while and its nice... There is a procedure per WAL split and ServerCrashProcedure doesn't block and wait till ALL WALs split before it can move forward; now it schedules all the WAL splits and then suspends itself freeing up the ProcedureExecutor.

> Enable procedure-based log splitting as default in hbase3
> ---------------------------------------------------------
>
>                 Key: HBASE-24632
>                 URL: https://issues.apache.org/jira/browse/HBASE-24632
>             Project: HBase
>          Issue Type: Sub-task
>          Components: wal
>            Reporter: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> Means changing this value in HConstants to false:
>    public static final boolean DEFAULT_HBASE_SPLIT_COORDINATED_BY_ZK = true;
> Should probably also deprecate the current zk distributed split too so we can clear out those classes to.



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