[
https://issues.apache.org/jira/browse/HBASE-24632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163998#comment-17163998
]
Michael Stack commented on HBASE-24632:
---------------------------------------
{quote} So here also once the work is given, the thread wont get blocked but
will yield?
{quote}
Thats right. The RPD will dispatch the split WAL job to the remote RS wrapped
in a ExecuteProceduresRemoteCall. Once the RPC delivers the job to the remote
RS, the RPD dispatcher is done (and its thread from the RPD executor of 128
threads is now idle again). Meanwhile the split WAL starts to run on the RS
side. When it is done, it will do a similar call back to the Master to tell it
success or failure but this is different RPC that originates at the RS.
HBASE-24766 is issue where I'll add some doc around this stuff. The questions
above are good. I said I'd do doc in this area a while ago. Let me do now.
> 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)
