On 14 Oct 2014, at 15:04 , Ingo Radatz <[email protected]> wrote:
> 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? It seems that the timeout is on HAproxy’s side. CouchDB won’t respond with a 204 for view requests, neither does Mochiweb on its own. The only place a 204 is even mentioned in the CouchDB source is when doing CORS preflight requests. Best Jan --
signature.asc
Description: Message signed with OpenPGP using GPGMail
