The issue I found turns out to have been an inefficiency in multipart parsing rather than an actual error (though it could cause crashes with very large attachments). But the fix went in to CouchDB 1.6, so the problem here is not obviously related.
The error comes from the code for sychronising document attachments: is there anything relating to attachments that distinguishes the failed databases from the successful ones? That might give a clue as to what's going on. Nick On Fri, 13 Jan 2017 at 09:15 Nick North <[email protected]> wrote: > I'm trying to dredge the details from the depths of my memory. There were > some replication problems with mime attachments, but I thought the patches > went in before CouchDB 1.6, in which case there should not be any problems > syncing with 2.0. I will check this evening and report back. > > Nick > > On Fri, 13 Jan 2017 at 08:35 Dave Cottlehuber <[email protected]> wrote: > > On Sun, 1 Jan 2017, at 14:36, Vishesh Mittal wrote: > > I am syncing all my databases from CouchDB 1.6 server to a CouchDB 2.0 > > server. > > > > Most of the databases sync correctly. However, some of them are not > > syncing. The log file shows the following error. Any clue? > > > > Thank you so much > > > > > > > > [error] 2017-01-01T13:27:46.123435Z couchdb@localhost emulator -------- > > Error in process <0.24284.71> on node couchdb@localhost with exit value: > > > {{nocatch,{mp_parser_died,noproc}},[{couch_att,'-foldl/4-fun-0-',3,[{file,"src/couch_att.erl"},{line,591}]},{couch_att,fold_streamed_data,4,[{file,"src/couch_att.erl"},{line,642}]},{couch_att,foldl,4,[{file,"src/couch_att.erl"},{line,595}]},{couch_httpd_multipart,atts_to_mp,4,[{file,"src/couch_httpd_multipart.erl"},{line,208}]}]} > > IIRC Nick came across something like this a few years ago, maybe he can > shed some light on it. > > A+ > Dave > >
