On Mon, Nov 5, 2012 at 7:27 AM, Dustin Sallings <[email protected]> wrote: > Benoit Chesneau <[email protected]> > writes: > >> Just ask around you how many people aren't changing the default port >> of couchdb and pur their servers in usual ip ranges you expect from a >> server. Imo a port change is a significant event. > > I am completely failing to understand what you're saying. This fails > for me on my laptop for three cases: > > 1. My home couchdb server (by hostname, only available from inside my > house) > 2. My work couchdb server (by hostname, available inside and outside, > but the IP addresses are different in each location). > 3. Iriscouch (by hostname, available everywhere on the same address) > > In all three cases, it can stop replication, but will resume again if > I restart. > Most of these cases already work if you are using the new _replicator api.
> Under what circumstances do you consider "stop replicating after > sleep, but start again if the user restarts CouchDB" good behavior? - local replications should always restart. - replication with remote should restart only if the remote didn't change and my network didn't change. In other cases I need to rely on a mecanism to validate that I can continue the replication. In that case I agree it can be automated and we have different solution to do it. But that should never be a default mecanism imo. - benoît
