You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: