hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-2195) Support cyclic replication
Date Thu, 08 Sep 2011 04:47:09 GMT

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

Lars Hofhansl commented on HBASE-2195:
--------------------------------------

I still think versioning on HLogKey should be kept internal.
Now that we store a version internally we can add more fields.

Hopefully Replication{Source|Sink} never have to know about that.
If they do, we can add a getVersion() method then.

See for example WALEdit, which does a similar hack for the version also does not extend VersionedWritable
and version is strictly internal.

What this experience shows is that everything new that is serialized should be versioned from
the beginning.

That all said, I am not emotionally attached to not extending VersionWritable :)
Let's just say I am +-0 on this.

> 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
>            Assignee: Lars Hofhansl
>         Attachments: 2195-v10.txt, 2195-v12.txt, 2195-v5.txt, 2195-v6.txt, 2195.txt
>
>
> 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

        

Mime
View raw message