On Tue, Feb 18, 2014 at 2:28 PM, Jan Lehnardt <[email protected]> wrote: > > On 18 Feb 2014, at 17:09 , Paul Davis <[email protected]> wrote: > >> On Tue, Feb 18, 2014 at 9:30 AM, Adam Kocoloski <[email protected]> wrote: >>> On Feb 18, 2014, at 11:38 AM, Jan Lehnardt <[email protected]> wrote: >>> >>>> On 31 Jan 2014, at 20:08 , Jason Smith <[email protected]> wrote: >>>> >>>>> However there is a pathological situation where you are >>>>> updating faster than the compactor can run, and you will get an infinite >>>>> loop (plus very heavy i/o and filesystem waste as the compactor is >>>>> basically duplicating your .couch into a .couch.compact forever). >>>> >>>> Just a little clarification on this point: CouchDB will try to catch up, >>>> I think 10 times, before giving up and reporting the result in the logs. >>>> >>>> Best >>>> Jan >>>> -- >>> >>> I'm not aware of any limit to the number of iterations executed by the >>> compactor. Regards, >>> >>> Adam >> >> Confirmed after a quick skim that compaction doesn't stop retrying. > > I stand corrected, but I could swear CouchDB used to do this in the old days. > > Jan > --
Never for compaction so far as I know. The replicator has an exponential backoff and stops after 10 failures IIRC.
