Thx Johannes, that works around it technically but in my case the requester wants to wait as long as the indexing takes.
We have the httpd/server_options configuration mentioned in the docs http://couchdb.readthedocs.org/en/1.6.1/config/http.html#httpd/server_options but i struggle to find/understand the docs about it. Am i right to look at: http://erldocs.com/R14Aextra/mochiweb/mochiweb_response.html greetings, ingo > Am 14.10.2014 um 15:34 schrieb Johannes Jörg Schmidt <[email protected]>: > > Hi Ingo, > > You know you can always query the view with ?stale=update_after to get the > current (outdated) view and trigger the indexing after the view has been > returned to the client. > > http://docs.couchdb.org/en/latest/api/ddoc/views.html?highlight=update_after > > Greetings > Johannes > > 2014-10-14 15:04 GMT+02:00 Ingo Radatz <[email protected]>: > >> I use a CouchDB 1.6.0 behind a HAproxy. The CouchDB gets bigger amounts of >> docs as bulk uploads. >> >> After an upload the next request triggers indexing as expected. Now my >> problem: >> >> When the indexing takes too long the CouchDB seems to request a 204 (seen >> in the haproxy.log) to the transparent HAproxy (which itself translates >> that to a 502 Bad Gateway). >> >> I there an timeout setting for the mochiweb server which can be increased?
