[
https://issues.apache.org/jira/browse/COUCHDB-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson updated COUCHDB-141:
-----------------------------------
Summary: Replication should respect since=N seq-num parameter
(was: Short-Cut replication initialisation for large databases that are
guaranteed to be equal)
Issue Type: Improvement (was: New Feature)
Affects Version/s: 1.0
(was: 0.9)
Description:
The changes feed has a since=Seq param which can be used to start listening
somewhere other than the beginning of the database history. The replicator
should respect this option as well.
This can also be used by administrators who are bringing a CouchDB instance up
from a file that was physically copied between servers.
was:In a situation where a large database is made available on multiple nodes
by copying over the .couch file and where multi-master-replication should keep
all nodes in sync, the initial replication in each direction takes quite some
time, trying to determine if all databases are in the same state. When we copy
the .couch files, they are guaranteed to be equal. It would be nice to be able
to tell CouchDB that it doesn't actually have to iterate through all dbs and
just accept the fact that we tell it that they are equal.
renamed this ticket to for a feature that is more flexible than the old one.
> Replication should respect since=N seq-num parameter
> ----------------------------------------------------
>
> Key: COUCHDB-141
> URL: https://issues.apache.org/jira/browse/COUCHDB-141
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
> Affects Versions: 1.0
> Reporter: Jan Lehnardt
> Priority: Minor
>
> The changes feed has a since=Seq param which can be used to start listening
> somewhere other than the beginning of the database history. The replicator
> should respect this option as well.
> This can also be used by administrators who are bringing a CouchDB instance
> up from a file that was physically copied between servers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
