Stuck on an issue?

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.

[Question] Multiple workers with Sanic

See original GitHub issue

I have a Sanic app using python-socketio. The Websocket connection only works with app.run(workers=1); otherwise, Invalid session ... is raised.

Although I uses the AsyncRedisManager for the AsyncServer, the app still doesn’t seem to use redis to store the sessions:

app = Sanic(__name__)

mgr = socketio.AsyncRedisManager("redis://127.0.0.1:6379/0")
sio = socketio.AsyncServer(async_mode="sanic", cors_allowed_origins=[], client_manager=mgr)
sio.attach(app)

Is there a way for python-socketio to support multiple workers on Sanic ?

Issue Analytics

State:
Created 4 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

miguelgrinbergcommented, Oct 27, 2019

@snguyenthanh Sanic does not do sticky session type load balancing when it runs multiple workers, so yes, you have to run multiple one worker Sanic apps, and put a proper load balancer that you can configure for sticky sessions.

0reactions

snguyenthanhcommented, Oct 28, 2019

I see. Thank you for the explanation.

I think I will just go with the multiple-1-worker-app approach.