Thanks Gregor for raising this question. I have a very similar setup and I am also concerned about how it will scale.
g jo Am Dienstag, den 06.12.2011, 10:29 +0100 schrieb Gregor Martynus: > Thanks Benoit! > > I'm sorry to keep bugging ... > > The problem is, at least for me, that I can't simply delete docs from the > _replicator db. It's a critical part of my couchDB setup. It is something > that excited me a lot a about couchDB, I just want to setup these > replications and then don't think about it any more, that's something that > the DB should just do – and let me relax. > > What I really don't understand is, _why_ the continuous replication keep > the db files open? I'm not an Erlang developer at all, sorry if this is a > dump question/thought, but shouldn't the continuous replication be > triggered only if a change happens in the db, instead of keeping it alive > all the time? Is this a bug or probably something that might be improved in > future? > > Thanks > > × Gregor > > On Tue, Dec 6, 2011 at 10:16 AM, Benoit Chesneau <bchesn...@gmail.com>wrote: > > > On Tue, Dec 6, 2011 at 10:11 AM, Gregor Martynus <gre...@martynus.net> > > wrote: > > > Thanks Benoit, I know about this setting. But at some point, this won't > > > work anymore. My question is if there is any way to stop continuous > > > replications to keep the db files active changes have been replicated? > > Does > > > that make sense? > > > > > > > > > > other way would be to queue changes events and when replicated dbs < > > max dbs open a new task if a change happened on this . Something like > > it. > > > > Otherwise to answer to your question, if you use the _replicator db > > you can interrupt a task by just deleting the doc. > > > > - benoît > >
