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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/09/19 23:26:35 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14141332#comment-14141332 ] 

stack commented on HBASE-10295:
-------------------------------

[~mantonov] This one sounds up you fellas' alley?  Let me backport the one the undoes table enable/disable.

> 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
>              Labels: beginner
>             Fix For: 0.99.1
>
>
> 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
(v6.3.4#6332)