[ https://issues.apache.org/jira/browse/COUCHDB-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446957#comment-15446957 ]
Nick Vatamaniuc commented on COUCHDB-3111: ------------------------------------------ For reference here is an example of a change feed request : {code} GET /rdyno_0000001/_changes?filter=rdyno_filterdoc%2Frdyno_filtername&feed=continuous&style=all_docs&since=%22334-g1AAAAIieJyV0MENgjAUgOGnmKAnR9AJjG2RlpPcHENbHg0SxJNn3UQ30U10EyzUBAkhgTRpk7b_d3gZAEwTB2GenzEmIaF8tTaLZOZhLEEtiqJIE0e6J3PhKqEiLfz2905CLc2utj8FKoUTuqGaIswuOcb6mMfY3Ydlv2_0WiqfR9ivP5T9tdFLznxNvF59PjE73MxhiHttIGFCoxhgPKzxrA0aKCLQH2C8rPH-nwX1Auw3S2t8rFHOQwGMdhXDNPOQYztMv-12jrg%22&timeout=10000 {code} > Default replicator change feed timeout too short > ------------------------------------------------ > > Key: COUCHDB-3111 > URL: https://issues.apache.org/jira/browse/COUCHDB-3111 > Project: CouchDB > Issue Type: Improvement > Reporter: Nick Vatamaniuc > > Current replicator change feeds are set up to timeout based on default > connection_timeout parameter divided by 3. Default connection timeout is > 30000 (msec). So replicator change feeds are torn down and established again > every 10 seconds. > That doesn't seem bad on a smaller scale but if there are 1000 replications > jobs on a server it would means tearing down change feed connections every 10 > msec. It seems like it might not be optimal so wanted to discuss it. > Looking at the commit which introduced 'div 3' behavior wondering if there is > anything to improve here: > https://github.com/apache/couchdb-couch-replicator/commit/ed447f8c01880c7f99f5829a8ef485fd8d399376 > Maybe keep div 3 but increase default connection timeout to 60 seconds? Or > maybe apply div 2 - 5 seconds, or have a minimum of 30 seconds? -- This message was sent by Atlassian JIRA (v6.3.4#6332)