[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844174#comment-16844174 ] stack commented on HBASE-9934: -- Thanks for doing this JIRA gardening [~gsbiju] > 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 >Assignee: 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 (v7.6.3#76005)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838984#comment-16838984 ] Biju Nair commented on HBASE-9934: -- Is this feature still needed and pursued? If not can it be closed? [~ishanc], [~lhofhansl] > 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 >Assignee: 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 (v7.6.3#76005)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819887#comment-13819887 ] Ishan Chhabra commented on HBASE-9934: -- [~nidmhbase] Lars' understanding is correct. That is why this should be specified at peer level and not CF level. Also, when per cf peer definition will be supported, this would fit in automatically at peer level. [~lhofhansl] Ill give this a shot. Can you assign this to me? > 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819871#comment-13819871 ] Lars Hofhansl commented on HBASE-9934: -- If I understood Ishan correctly, he wants to be able replicate the same change to some cluster in a chain and directly to some other clusters. > 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819694#comment-13819694 ] Lars Hofhansl commented on HBASE-9934: -- Fixed the comment :) OK I get it, each source-sink pair has to be declared to only do one hop. Hmm. As you said it makes sense to expose this via addPeer. Then where to put this information? Maybe in ZK. Then we need to a good way to check that information when it is time to replicate at the sink for that data. Maybe it's not quite as simple as I thought. Do you have time to work up a patch [~ishanc]? > 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819610#comment-13819610 ] Ishan Chhabra commented on HBASE-9934: -- Ok. The above one is not right again. The spaces are removed when I save and the weird strike though comes in. C1 and C2 are connected to C3 and not C4. > 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819608#comment-13819608 ] Ishan Chhabra commented on HBASE-9934: -- That is the first proposal. It will not work where people have a mixed setup. The 2nd one, where a link (source, sink) pair is specified to be belonging to a mesh network should work better, but might be more dev work. Also, when you were cleaning my comment, the diagram got changed. Below is the fixed version. C4 <-> C3 <-> C5 <-> C6 / \ C1 - C2 > 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819538#comment-13819538 ] Lars Hofhansl commented on HBASE-9934: -- Thanks [~ishanc], trying to follow. :) So if I understand you correctly you want be able to say at the source to replication only exactly one hop. That might be the typical setup anyway. I do not think many folks will use "cyclic replication" (HBASE-2195) > 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)
[jira] [Commented] (HBASE-9934) Mesh replication (a.k.a. multi master replication)
[ https://issues.apache.org/jira/browse/HBASE-9934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819517#comment-13819517 ] Ishan Chhabra commented on HBASE-9934: -- Changed the title to Mesh replication as that describes the feature request better. Multi-master replication may not be the best term but is used by the DBA community for these setups for MySQL or other RDBMS. > 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)
