hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10295) Refactor the replication implementation to eliminate permanent zk node
Date Mon, 07 Apr 2014 09:05:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961726#comment-13961726
] 

Mikhail Antonov commented on HBASE-10295:
-----------------------------------------

I'm thinking if this jira kind of fits the umbrella of HBASE-10909?

> 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
>             Fix For: 0.99.0
>
>
> Though this is a broader and bigger change, it original motivation derives from [HBASE-8751|https://issues.apache.org/jira/browse/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.2#6252)

Mime
View raw message