[
https://issues.apache.org/jira/browse/HBASE-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883712#action_12883712
]
ryan rawson commented on HBASE-2804:
------------------------------------
it would make sense to 'shard' ICV by datacenters, where each datacenter gets
it's own ICV column then anyone wishing to know the total would just get all
columns and sum. Different datacenters would not overwrite each other. The
only problem is this is more of an application level thing, and isnt baked into
the API anywhere setting people up for failure down the road.
The problem with doing something like shipping deltas is that it becomes
difficult to bring up a new cluster, since the cluster will need a 'starting
point' combined with a sequence of deltas that must mesh perfectly or else the
replica cluster will be out of sync.
> [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.
