Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <1650166E173D354E9382181CA2DA9B0C0BEB1A7BE4@GSCMEUP05EX.firmwide.corp.gs.com>
References: 
 <1366713650.19418.140661221559174.69383B1D@webmail.messagingengine.com>
	<1650166E173D354E9382181CA2DA9B0C0BEB1A7BE4@GSCMEUP05EX.firmwide.corp.gs.com>
Date: Tue, 23 Apr 2013 12:45:56 +0100
Message-ID: 
 <CABvT1DHicxwEUKvvTPGQC9k9_6vBRe5-Vv6QDhPskL3+zTxcSw@mail.gmail.com>
Subject: Re: Problem with restart of continuous replication
From: Robert Newson <rnewson@apache.org>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

I'm with Martyn there. Trust, but verify. :)

B.

On 23 April 2013 12:23, Pearce, Martyn [Sec Div] <Martyn.Pearce@gs.com> wrote:
> If you care, monitor.  Not impugning anybody's fantastic hard work, but bugs exist, edge cases will be found, etc.
>
> -----Original Message-----
> From: Calle Arnesten [mailto:calle.arnesten@codekick.com]
> Sent: Tuesday, April 23, 2013 11:41 AM
> To: user@couchdb.apache.org
> Subject: Re: Problem with restart of continuous replication
>
>> I would set the retry limit to infinity, I think you'll agree with me
>> that a persistent replication that gives up is hardly persistent at
>> all;
>
> Thanks, will do that. With that in place, is there really a need to monitor the replication itself?
> I do have monitoring (using monit) that CouchDB is running and responds.
>
> /Calle