Skip to content

Conversation

@j3k0
Copy link
Contributor

@j3k0 j3k0 commented Nov 1, 2016

When some HTTP requests take too long, the queue of requests gets filled up and other requests, that shouldn't fail, fail too with timeouts / too long to process errors.

Logs showed errors like this: [simple_httpclient:137:fetch_impl] max_clients limit reached

So it seems I fell into this case: http://stackoverflow.com/questions/33411493/max-clients-limit-reached-request-queued-tornado

This is a simple (naive?) attempt to fix those errors (based on the stackoverflow answer). Increasing the max number of concurrent requests being processed by tornado seems to fix my problems, on my setup.

When some HTTP requests take too long, the queue of request gets filled
up and other requests fail with timeouts / too lon to process errors.

This is a simple (naive?) attempt to fix those errors, by increasing the
max number of concurrent requests being processed.
@garrettheel
Copy link
Collaborator

Thanks for contributing, @j3k0! Would you mind making this a configuration option and only explicitly setting the max number of connections if it is set?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants