-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove workspace id from websocket connection path to master #1787
Labels
kind/task
Internal things, technical debt, and to-do tasks to be performed.
Milestone
Comments
@vparfonov - is there a PR for this? Why add to 4.6 milestone if PR is not readied. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Workspace statuses are now tracked by various websocket connections per workspace id. It creates a lot of problems in order to handle the high number of websockets. (especially in dashboard)
Providing one connection with various channels will decrease the number of persistent websocket connections. Thus the clients will be able to use one connection to listen statuses of all workspaces, instead on multiple ones.
The text was updated successfully, but these errors were encountered: