Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAJNb-9pTHs_AUEt3pQ08UxVFpDQ-731=A=-TvE+Yu_DVucsMzw@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>
	<CAJNb-9pTHs_AUEt3pQ08UxVFpDQ-731=A=-TvE+Yu_DVucsMzw@mail.gmail.com>
Date: Tue, 6 Dec 2011 10:29:30 +0100
Message-ID: 
 <CA+5KyPSAPig__TUbMpUM4zx7A0fCbm8Z1bubekGGuB-OsuROZQ@mail.gmail.com>
Subject: Re: all_dbs_active error and continuous replications
From: Gregor Martynus <gregor@martynus.net>
To: dev@couchdb.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3ba4d38988e804b36912c5

--e89a8f3ba4d38988e804b36912c5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 =E2=80=93 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

=C3=97 Gregor

On Tue, Dec 6, 2011 at 10:16 AM, Benoit Chesneau <bchesneau@gmail.com>wrote=
:

> On Tue, Dec 6, 2011 at 10:11 AM, Gregor Martynus <gregor@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=C3=AEt
>

--e89a8f3ba4d38988e804b36912c5--