[
https://issues.apache.org/jira/browse/HBASE-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884842#action_12884842
]
Jonathan Gray commented on HBASE-2804:
--------------------------------------
you can pay the cost at write-time by executing double writes to each DC, or
you can pay the cost at read-time by executing double reads from each DC.
i think it's worth at least trying to get some "eventually consistent"
master-master counters via async replication. is the 'starting point' any more
complex than normal replication? i guess if you are considering duplicate
writes as idempotent (they kind of are but not completely) it's different but
if not it doesn't seem any more difficult, the ordering of operations does not
matter in this case only that the operations are strictly not idempotent.
> [replication] Support ICVs in a master-master setup
> ---------------------------------------------------
>
> Key: HBASE-2804
> URL: https://issues.apache.org/jira/browse/HBASE-2804
> Project: HBase
> Issue Type: New Feature
> Reporter: Jean-Daniel Cryans
> Fix For: 0.21.0
>
>
> Currently an ICV ends up as a Put in the HLogs, which ReplicationSource ships
> to ReplicationSink that in turn only recreates the Put and not the ICV
> itself. This means that in a master-master replication setup where the same
> counters are implemented on both side, the Puts will actually overwrite each
> other.
> We need to find a way to support this use case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
