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

The state of Socket.IO rooms are only in memory on the api #335

Open
2 tasks done
davidvandusen opened this issue Mar 8, 2022 · 0 comments
Open
2 tasks done

The state of Socket.IO rooms are only in memory on the api #335

davidvandusen opened this issue Mar 8, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@davidvandusen
Copy link
Member

Expected behaviour

Restarting the api does not lose the state of which sockets are in which rooms.

Actual behaviour

Restarting the api causes all the rooms that sockets have joined to be lost because that state is not persisted (or shared between api instances, for that matter.)

Details and resources

Socket.IO has adapters for this sort of thing, such as https://socket.io/docs/v4/redis-adapter/.

Checklist

  • This issue is linked to the appropriate project.
  • This issue has appropriate labels.
@davidvandusen davidvandusen added the bug Something isn't working label Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant