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

LiveKit Resiliency #1426

Open
pentreathm opened this issue Jan 20, 2023 · 0 comments
Open

LiveKit Resiliency #1426

pentreathm opened this issue Jan 20, 2023 · 0 comments
Labels

Comments

@pentreathm
Copy link
Member

pentreathm commented Jan 20, 2023

In production currently, there are 2 flavors of LiveKit: Cloud and Hosted service.
This still represents a weak failure point if the LiveKit cloud stops working. A disaster recovery process or a fallback mechanism should be implemented to mitigate this. For the time being, this can be accomplished by changing the branch to comms-v2 and starting the node on P2P comms but this requires maintaining 2 branches of the catalyst-owner repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant