Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SocketIO seems to be not working with multiple workers in gunicorn #35

Closed
b-3-n opened this issue Jun 9, 2014 · 2 comments
Closed

SocketIO seems to be not working with multiple workers in gunicorn #35

b-3-n opened this issue Jun 9, 2014 · 2 comments

Comments

@b-3-n
Copy link

b-3-n commented Jun 9, 2014

Title says it pretty much. Using more than one worker leads to failed requests (502 bad gateway). Actually I came to the assumption that no matter which number of workers is set there will be always one valid worker while very other worker fails to serve requests. This assumption is based on the circumstance that some requests still are served when using multiple workers and the number of failed requests increases with the number of workers specified.

I'm sorry if this is a documented behavior - did not find anything about it.

@miguelgrinberg
Copy link
Owner

gevent-socketio uses memory structures to keep track of socket connections, so it won't work with multiple workers. See this issue: abourget/gevent-socketio#112.

Now keep in mind that a gevent based server does not need multiple workers to handle concurrent clients, a single worker can easily handle thousands of connections, if not more.

@b-3-n
Copy link
Author

b-3-n commented Jun 9, 2014

Okay. Thank you for the information.

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

No branches or pull requests

2 participants