[
https://issues.apache.org/jira/browse/HBASE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095480#comment-13095480
]
Jean-Daniel Cryans commented on HBASE-2195:
-------------------------------------------
bq. Better to group edits and provide the UUID once in the wrapper perhaps?
ReplEdit, like WALEdit? At least would cut down from 128 bits every edit always.
bq. Grouping edits is good idea.
Right now HLogKey has the byte that identifies the cluster, and there's only
one per WALEdit. Meaning it's already grouped.
bq. What the general thought here? Do this? Or increment the versions of the
Put and Delete classes and add a new byte member for the cluster id?
One one hand, if it's an attribute it means there's a possibility we can ask
the cluster if it supports replication and in the case it doesn't then you
don't have to add it. On the other hand, it's more complex.
You could also add it in MultiAction so that grouped Puts and Deletes wouldn't
have to carry the same information N times.
> Support cyclic replication
> --------------------------
>
> Key: HBASE-2195
> URL: https://issues.apache.org/jira/browse/HBASE-2195
> Project: HBase
> Issue Type: Sub-task
> Components: replication
> Reporter: Jean-Daniel Cryans
>
> We need to support cyclic replication by using the cluster id of each HlogKey
> and stop replicating when it goes back to the original cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
