Hi Vovan, If we are talking Couch 1.6, the attribute *retries_per_request* controls a number of attempts a current replication is going to do to read _changes feed before giving up. The attribute *max_replication_retry_count* controls a number of attempts the whole replication job is going to be retried by a replication manager. Setting this attribute to “infinity” should make the replicaton manager to never give up.
I don’t think the interval between those attempts is configurable. As far as I understand it’s going to start from 2.5 sec between the retries and then double until reached 10 minutes, which is going to be hard upper limit. Regards, Eric > On Jun 20, 2017, at 00:31, Vladimir Kuznetsov <vova...@gmail.com> wrote: > > Hi, > > I'm currently exploring CouchDB replication and trying to figure out the > difference between *max_replication_retry_count* and *retries_per_request* > configuration options in *[replicator]* section of configuration file. > > Basically I want to configure continuous replication of local couchdb to the > remote instance that would never stop replication attempts, considering > potentially continuous periods of being offline(days or even weeks). So, I'd > like to have infinite replication attempts with maximum retry interval of 5 > minutes or so. Can I do this? Do I need to change default configuration to > achieve this? > > thanks, > --Vovan
