chiraganand commented on issue #4373: URL: https://github.com/apache/couchdb/issues/4373#issuecomment-1398665264
I tried v3.3.1 and was able to reproduce the error exactly after 800 requests on an EC2 _m4.large VM_. Some more observations: 1. If I reduced the number of concurrent threads to 5 from 10 then no request would timeout among a total of 1000 requests. 2. I would not see this same behaviour on a bigger machine (_m4.xlarge_). All the 1000 requests would respond before timing out on the bigger machine with 10 concurrent threads. 3. Surprisingly, I encountered the original issue while there was only one active user not 10 concurrent users. I used JMeter to pin down the problem. > If there are proxies in between they could also be blocking or timing out the connections. It might help inspecting logs there for connection states. On _m4.large_ VM there are no proxies but on _m4.xlarge_ there is a Nginx reverse proxy. Because of an internal requirement we had to wipe off the core databases on both the servers and I am now unable to reproduce this issue. There is not even a single error in 100 iterations with 50 concurrent threads! I guess I will populate more data and then test again. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
