Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"Connection reset by peer" failure When doing local test with lost ( >1000) concurent users
See original GitHub issueI’m using locust 0.7.5 , when I try to do a local (on my ubuntu 16.04) load test on a tornado web service, with a high number of concurrent users, a certain percentage of the requests (~8%) fail with the error
"ConnectionError(ProtocolError('Connection aborted.', error(104, 'Connection reset by peer')),)"
According to http://www.itmaybeahack.com/homepage/iblog/architecture/C551260341/E20081031204203/index.html , it seems to be a known python issue , which also seems to rule out a problem on the server side (which is correlated by the fact that I see no error or warning on the server side)
Is this a known locust issue ? If yes what are the workaround ?
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Connection reset by peer means the server (your target host) has closed its connection to Locust. With a high probability it has nothing to do with Locust and everything to do with your target server.
You might find some hints here: https://github.com/locustio/locust/wiki/FAQ#increase-my-request-raterps
Thank you