Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 16 May 2013 15:00:40 +0300
From: svilen <az@svilendobrev.com>
To: user@couchdb.apache.org
Subject: Re: how to wake up error replication
Message-ID: <20130516150040.4d97c890@svilendobrev.com>
In-Reply-To: 
 <CAFZfYnCSd4VgdjiGe15dzOKoxV9D+9nGuEeKYTj6LyvsTtuLrA@mail.gmail.com>
References: 
 <CAFZfYnCSd4VgdjiGe15dzOKoxV9D+9nGuEeKYTj6LyvsTtuLrA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

from the doc: https://gist.github.com/fdmanana/832610
 * >What is the recommended way to restart a replication that 
 * is currently in the error state?
 * Edit the doc and remove the field "_replication_state".
 * Or create another identical doc (same source, target, etc).


On Thu, 16 May 2013 13:52:46 +0200
Tibor Gemes <tibber@gmail.com> wrote:

> I have a notebook on which there is a couchdb instance. I have a
> continuous replication document in the _replicator database.
> Let's suppose I suspend my notebook and wake it up in a different
> network where there is no network connection. The replication
> document switches its state to error.
> If I later move back to a different network where I can reach the
> source couchdb again then the replication will turn to 'triggered'
> after a while, but how can I enforce it to recheck the remote end? Is
> there any api call which would force to revalidate the state of the
> replication?
> 
> T