couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Ringo <>
Subject Re: _replication database pruning
Date Thu, 19 Jan 2012 11:02:25 GMT
This is the recommended way of starting a replication no?

curl -H 'Content-Type: application/json' -X POST 
http://localhost:5984/_replicator -d '{"source": 
"", "target": ""}'

It also is the way the library I am using (CouchCocoa) does it.

I realise one can post to /_replicate (as opposed to _replicator), but 
then there's no recovery if the database is restarted, right?

What else should I be using?

Robert Newson wrote:
> Why are you using the _replicator db for one-off replications in the
> first place? :)
> B.
> On 19 January 2012 04:07, Steven Ringo<>  wrote:
>> I notice the _replication database fills up with entries as one-off
>> replications take place. In the case of many replications being fired off
>> (e.g. filtered per-user) the database may end up getting large.
>> Like log file rotation, etc. is there a way to automatically prune or do
>> something to keep it cleaned?
>> Thanks,
>> Steve

View raw message