Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 74.125.83.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+5KyPRyFN+UYfYho7_T0fJYOHEz5kfURxk1zd7GKPrchN4b+A@mail.gmail.com>
References: 
 <CA+5KyPRuC3JmbyXamSZeHjxqxxEDSCKTdYEEZ+KRsPbjvbHo2g@mail.gmail.com>
	<CAJNb-9obJkSUAGHhV9atDUf6x+fVFARTUsom1QnXK=eQyrb=6Q@mail.gmail.com>
	<CA+5KyPRyFN+UYfYho7_T0fJYOHEz5kfURxk1zd7GKPrchN4b+A@mail.gmail.com>
Date: Tue, 6 Dec 2011 10:16:17 +0100
Message-ID: 
 <CAJNb-9pTHs_AUEt3pQ08UxVFpDQ-731=A=-TvE+Yu_DVucsMzw@mail.gmail.com>
Subject: Re: all_dbs_active error and continuous replications
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Dec 6, 2011 at 10:11 AM, Gregor Martynus <gregor@martynus.net> wrot=
e:
> 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? Do=
es
> 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=EEt