[
https://issues.apache.org/jira/browse/HBASE-24632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163551#comment-17163551
]
Anoop Sam John commented on HBASE-24632:
----------------------------------------
So for every WAL file, it will add a sub procedure in ProcedureExecutor and
that in turn add entries for RemoteProcExecutor correct? So at this stage also
these Sub proc executing threads will yield once the split proc is submitted to
RemoteProcExecutor ? And there in that executor we have 128 threads by
default. Will that wait once it issue split request to RS for split? Or will
that also yield? If former, then we will get big backlog in a bigger cluster
with many RS down and every having many WALs to split
> 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)
