gunicorn + socketio + multiple workers problem

413 views
Skip to first unread message

arnuschky

unread,
Oct 8, 2013, 3:40:37 PM10/8/13
to gevent-...@googlegroups.com
Hello,

we're facing a weird problem with our gunicorn installation. We're using socketio to transfer data between the website and the backend. We just noticed that when using more than one gunicorn worker, the behavior becomes unreliable. It's similar to what was described in the links below. 

We haven't noticed this problem until today as we added a new functionality (a new post message, not sure if this is related) For some reason the problem did not appear before. The behavior is highly non-deterministic as the data sometimes comes through.

Is there any progress on the solution of this problem? Is it being worked on? Can we do anything to help fixing this?

Cheers,
Arnuschky

https://github.com/abourget/gevent-socketio/issues/132

Alexandre Bourget

unread,
Oct 8, 2013, 5:18:52 PM10/8/13
to gevent-...@googlegroups.com

I replied in the first issue.

I'd be curious to see how other socket.io implementations deal with this issue.. since it is really due to statelessness being assumed by gunicorn and reverse proxies at many levels. In a stateless world, we don't really care if you hit the same server for your next request.  Socket.IO deals with stateful connections.

Looking into the way people scale the nodejs version might be helpful.

Alexandre

--
You received this message because you are subscribed to the Google Groups "gevent-socketio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gevent-socket...@googlegroups.com.
To post to this group, send email to gevent-...@googlegroups.com.
Visit this group at http://groups.google.com/group/gevent-socketio.
For more options, visit https://groups.google.com/groups/opt_out.

Franck

unread,
Oct 17, 2013, 3:40:10 PM10/17/13
to gevent-...@googlegroups.com, al...@bourget.cc
Hello,
I'm sure about the consequence for the answer.

It seems to mean that for the moment, we can't start more than 1 socket io worker.
Also i use for the moment, gunicorn 0.16.1, other new versions have problem with some missing value in the environment.

Franck
Reply all
Reply to author
Forward
0 new messages