jlami opened a new issue #1843: replication error, atts_since limit on heavy 
conflicted doc
URL: https://github.com/apache/couchdb/issues/1843
 
 
   Replication is failing due to a request failing which seems related to a 
`atts_since` limit.
   
   ## Expected Behavior
   Requesting a document with 30+ atts_since entries should work. But only when 
I remove some entries in the request array am I capable of getting a valid 
response.
   
   ## Current Behavior
   Gives 400 error.
   
   ## Context
   The problem occurred on a database where one document had a lot of 
conflicts. It looks like for each conflict an entry into atts_since is added to 
get new revisions since the conflict branches. But today I noticed the 
replication was hanging/looping and causing a lot of errors in the log. I saw 
errors mentioning the GET request with atts_since (error on windows, but later 
as notice when trying on Linux).
   ```
   emulator -------- Error in process <0.1903.10> on node couchdb@localhost 
with exit value:
   
{function_clause,[{couch_replicator_api_wrap,'-open_doc_revs/6-fun-1-',[400,[{"Content-Length","0"},{"Date","Tue,
 08 Jan 2019 14:58:13 GMT"},{"Server","MochiWeb/1.0 (Any of you quaids got a 
smint?)"},{"Strict-Transport-Security","max-age=31536000"}],#Fun<couch_replicator_httpc.0.15481832>],[{file,"src/couch_replicator_api_wrap.erl"},{line,254}]},{couch_replicator_httpc,process_stream_response,5,[{file,"src/couch_replicator_httpc.erl"},{line,205}]},{couch_replicator_httpc,send_req,3,[{file,"src/couch_replicator_httpc.erl"},{line,76}]}]}
   Replication crashing because GET 
https://servername/db/conflicteddoc?atts_since=%5B%222-1631949226f78c645dde972daa1318a3%22%2C%222-47dcd3afe7e16850ebec40ce2f190351%22%2C%222-804d2065909cfd135d7c2a69d81733b1%22%2C%222-91e9a8310a73757819f48f9035e17fc4%22%2C%222-9329e8bb6290a6e10322cba14839bb62%22%2C%222-ac0c261b873d070d1817bfea3e0d1e57%22%2C%222-d5743060c5dcb5882f4eba4d724a7b48%22%2C%222-e14ae63e9d12f2dff7d683f249bf7f86%22%2C%222-fd7099b4b667c55093268f2589028457%22%2C%222-fdf27027813c424d8a5dc65a48a1f9e7%22%2C%22502-0f6282c92965d792e5cfd0a218dc90e1%22%2C%22576-74f1baae10dc93634c8f664a7080792f%22%2C%22693-23827d51bb67119753a8d43a47d7d90c%22%2C%22817-706ca2dadd94dd05067924a4cf3d62ae%22%2C%22925-83f6a73f51e1b47b9c745a81de306463%22%2C%221435-4ec081205b9fd732f9d0db597a2d9d61%22%2C%221663-0e9ffd5403634b8e127c2ad496ef30bd%22%2C%221875-921c203e382a203b31831fa8235ee293%22%2C%222089-81ca3e663a9e8b4d1eafe5f0a7c139ef%22%2C%222224-c4cab42628e96345b34bb509062b1e6c%22%2C%222575-4f437ad237ed3a5c0e979d9f63168cbb%22%2C%222752-c7d6fb9febf1c463e758a89fce901df7%22%2C%222774-8fed8922aefa1262d7cb67798edd69cc%22%2C%222991-e55c6ff1a19604904d7e83cdba3db2f3%22%2C%223105-17b3e2194c6cf2d406fed05665883213%22%2C%223145-a752288c0690f54ace8f82f58015bef7%22%2C%223338-c17c0cf94b92b67bde2611744e5c05fc%22%2C%223572-514320d19c476f068db5065cd04c3553%22%2C%223754-21e842ffb0320b44103e04718aa8b671%22%2C%224262-19ccbdc6f71b8aabf18dd31cbd1e5cdf%22%2C%224698-c74d7c5b75c7d4f0004f3328251de391%22%2C%226485-f75dc4ea029b0934a9788f21bc911bbb%22%2C%226525-c332948ceeabde42097167f7800afc6f%22%2C%226624-48315fc928413903f57cb90fdbb13da4%22%2C%226719-1a26fb75b6cbdfa064a10464e67a46fd%22%2C%226812-fed431bf100b563e2a10cae6661e9bbf%22%2C%226843-de87dbff1483490cb2ecb89ab51197e4%22%2C%227154-cbb96c93c6e5585e45f7cd95f9e40f22%22%2C%227165-80b31ecaa0a3eaf70b9a33513cb209d3%22%2C%227604-c7e1cbd8067fca122b00c43de08a1878%22%2C%227953-e1abb0cf7967b46ef45c7a251a0fd938%22%2C%228023-141bf3a1762377883f9995f584030b84%22%2C%228125-82b72ebbfcda41809f456b45f9c8f541%22%5D&revs=true&open_revs=%5B%228138-5dbae82b30eb49509cdf32f743c7ab58%22%5D&latest=true
 failed
   ```
   
   Other documents seem to replicate fine. But even after I deleted the 
conflicting revs did the error remain.
   
   2.2.0 on Windows
   2.3.0 on Linux

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to