[
https://issues.apache.org/jira/browse/HBASE-21729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingyun Tian updated HBASE-21729:
---------------------------------
Description: If procedureV2 based WAL splitting is enabled,
CoordinatedStateManager will not be initialized and will be useless when we
switch to procedureV2 WAL splitting. To remove this class in the futrue, we
need to extract getProcedureMemberRpcs() and getProcedureCoordinatorRpcs(),
which are actually not related to WAL splitting. (was: If procedureV2 based
WAL splitting is enabled, CoordinatedStateManager will not be initialized. Then
ProcedureCoordinatorRpcs and ProcedureMemberRpcs will make backup not work. Let
me extract these two method to another class.)
> Extract ProcedureCoordinatorRpcs and ProcedureMemberRpcs from
> CoordinatedStateManager
> -------------------------------------------------------------------------------------
>
> Key: HBASE-21729
> URL: https://issues.apache.org/jira/browse/HBASE-21729
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jingyun Tian
> Assignee: Jingyun Tian
> Priority: Major
> Attachments: HBASE-21729.master.001.patch,
> HBASE-21729.master.002.patch
>
>
> If procedureV2 based WAL splitting is enabled, CoordinatedStateManager will
> not be initialized and will be useless when we switch to procedureV2 WAL
> splitting. To remove this class in the futrue, we need to extract
> getProcedureMemberRpcs() and getProcedureCoordinatorRpcs(), which are
> actually not related to WAL splitting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
