I tried using Mango and the index builds without errors and much faster. This is great, however I am trying to understand how this fits with the rest of CouchDB. In particular, with Mango it looks like we no longer "You query your view to retrieve the view result" and this would imply that converting couchapps to Mango is not trivial. Is this correct?
Regards, Gustavo Delfino -----Original Message----- From: Joan Touzet [mailto:[email protected]] Sent: Thursday, February 23, 2017 5:43 PM To: [email protected] Subject: Re: views failing due to fabric_worker_timeout and OS process timed out Switching to Mango would be best. :) ----- Original Message ----- > From: "Gustavo Delfino" <[email protected]> > To: [email protected], "Joan Touzet" <[email protected]> > Sent: Thursday, February 23, 2017 3:19:31 PM > Subject: RE: views failing due to fabric_worker_timeout and OS process > timed out > > I installed CouchDB 1.6.1 on a separate machine and copied all the > data. Initially it failed too, but then I read about increasing the > memory to couchjs.exe and now it seems to be working (the view is 50% > ready after a few hours): > > http://stackoverflow.com/questions/21273736/couchdb-views-os-process-e > rror-big-documents > > I changed [query_servers] javascript from > > ./couchjs.exe ../share/couchdb/server/main.js > > to > > ./couchjs.exe -S 268435456 ../share/couchdb/server/main.js > > This is four times the default amount of memory. > > Unfortunately this doesn't work with CouchDB 2.0.0 (see > https://github.com/apache/couchdb-couch/pull/216 ) > > Do you think that switching to Erlang view server would better for > handling big documents? > > Regards, > > Gustavo Delfino
