[
https://issues.apache.org/jira/browse/ACCUMULO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006202#comment-14006202
]
ASF subversion and git services commented on ACCUMULO-378:
----------------------------------------------------------
Commit 59177233fd903d5c69592c67e603c58bc2a0ed2a in accumulo's branch
refs/heads/ACCUMULO-378 from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=5917723 ]
ACCUMULO-378 When re-syncing to where we left off on reads, we need to track
all tids for our table
Fixes an issue where when the DEFINE_TABLET wasn't contained in the batch
of log entries that we were reading, we ignored all of the mutations.When
we read past all of the old data, we still need to track the tids
for the table which we're replicating.
> Multi data center replication
> -----------------------------
>
> Key: ACCUMULO-378
> URL: https://issues.apache.org/jira/browse/ACCUMULO-378
> Project: Accumulo
> Issue Type: New Feature
> Reporter: Sapan Shah
> Assignee: Josh Elser
> Priority: Minor
> Fix For: 1.7.0
>
>
> The use case here is where people have multiple data centers and need to
> replicate the data in between them. Accumulo can model this replication
> after the way that HBase currently handles the replication as detailed here
> (http://hbase.apache.org/replication.html).
> There will be one master Cluster and multiple slave clusters. Accumulo will
> use the Master-Push model to replicate the statements from the master
> clusters WAL to the various slaves WALs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
