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

Is it possible to auto scale JMS pods ( web, prosody and jicofo) using Horizontal pod autoscaling ?? #89

Closed
Govind10g opened this issue Sep 4, 2023 · 2 comments
Labels
duplicate This issue or pull request already exists enhancement New feature or request

Comments

@Govind10g
Copy link

Govind10g commented Sep 4, 2023

Hi Team,

Wanted to understand, Is it possible to auto scale jitsi kubernetes pods i.e. WEB, JICOFO and PROSODY ??

In my architecture, I have a load balancer in front Kubernetes cluster to access the Jitsi UI application.
And JVB is running on EC2 server not in the kubernetes cluster and for JVB we are running multiple server to handle the load.
But for JMS (WEB, PROSODY and JICOFO) I don't know How we can auto scale ?? Or Is it possible or not ??

Please help me.

@saghul @spijet

@spijet
Copy link
Collaborator

spijet commented Apr 12, 2024

Hello @Govind10g!

It might be possible to implement the Horizontal Pod Autoscaling for the web component: it's stateless, so it should be relatively safe to scale it arbitrarily. I'm not sure about Jicofo, but Prosody is a stateful service that has to keep track of all the active user sessions and capabilities, so it might be much harder to implement autoscaling for it.

Do you have any specific issues with either of those components, which results in high utilization for them? How many rooms/users do you usually have accessing your Jitsi Meet installation?

@spijet spijet added duplicate This issue or pull request already exists enhancement New feature or request labels Apr 23, 2024
@spijet
Copy link
Collaborator

spijet commented Apr 23, 2024

I'm going to close this issue in favour of #111, because it's used to track the region sharding feature. If you have any additional information — feel free to post it here or there.

@spijet spijet closed this as completed Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants