hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Demai Ni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
Date Tue, 12 Nov 2013 01:30:17 GMT

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

Demai Ni commented on HBASE-9934:
---------------------------------

if expose this (one-hop) property through addPeer, that will impact everything replicated
to that particular peer. How about expose it at colfamily level? For example, we turn on replication
of a colfam by set 'REPLICATION_SCOPE' to a none-zero value. maybe we can reuse this field?


> Mesh replication (a.k.a. multi master replication)
> --------------------------------------------------
>
>                 Key: HBASE-9934
>                 URL: https://issues.apache.org/jira/browse/HBASE-9934
>             Project: HBase
>          Issue Type: New Feature
>          Components: Replication
>            Reporter: Ishan Chhabra
>            Priority: Minor
>
> This is to setup NxN replication.
> See background discussion here: 
> http://mail-archives.apache.org/mod_mbox/hbase-user/201311.mbox/%3CCAOiuM-4UMmLA7UHMp4hhjpLWUrHDxg1t4tN4aWvnZUMcTxG%2BKQ%40mail.gmail.com%3E
> We can add a new mode in replication to not forward edits from other clusters. Not sure
what should be done when some clusters are configured with this setting and some aren't.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message