hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feng Honghua (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-10295) Refactor the replication implementation to eliminate permanent zk node
Date Wed, 08 Jan 2014 03:40:51 GMT

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

Feng Honghua updated HBASE-10295:
---------------------------------

    Summary: Refactor the replication  implementation to eliminate permanent zk node  (was:
Refactor the implementation of replication to eliminate permanent zk node)

> 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: Feng Honghua
>            Assignee: Feng Honghua
>             Fix For: 0.99.0
>
>
> Though this is a more 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.1.5#6160)

Mime
View raw message