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

Posted to dev@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2022/06/12 13:02:00 UTC

[jira] [Resolved] (HBASE-10295) Refactor the replication implementation to eliminate permanent zk node

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

Duo Zhang resolved HBASE-10295.
-------------------------------
    Resolution: Duplicate

Duplicated by HBASE-15867.

> Refactor the replication  implementation to eliminate permanent zk node
> -----------------------------------------------------------------------
>
>                 Key: HBASE-10295
>                 URL: https://issues.apache.org/jira/browse/HBASE-10295
>             Project: HBase
>          Issue Type: Bug
>          Components: Replication
>            Reporter: Honghua Feng
>            Priority: Critical
>
> Though this is a broader and bigger change, it original motivation derives from HBASE-8751: the newly introduced per-peer tableCFs attribute should be treated the same way as the peer-state, which is a permanent sub-node under peer node but using permanent zk node is deemed as an incorrect practice. So let's refactor to eliminate the permanent zk node. And the HBASE-8751 can then align its newly introduced per-peer tableCFs attribute with this *correct* implementation theme.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)