Use multiple bridges about jitsi-meet HOT 8 CLOSED

The bridge in itself is quite scalable so this could wait a while

from jitsi-meet.

Some XMPP servers also support a special round-robin behaviour for having multiple components connected with the same hostname, so we might not have to solve this ourselves.

from jitsi-meet.

We realized that this is becoming more important because we can't otherwise update the server non-disruptively and have to wait for all conferences to end.

from jitsi-meet.

let's talk to matthew at fosdem. Prosody either has a feature for it or will add it without alot of work.

from jitsi-meet.

Sounds like a plan. Ideally what we'd need is for this to work a bit like the combination of SRVs and A/AAAA records. This would allow us to handle both load-sharing and failover. Something like

mainbridge1.example.com Prio1
mainbridge2.example.com Prio1

failoverbridge1.example.com Prio2
failoverbridge2.example.com Prio2

from jitsi-meet.

it's more complicated. The component manager needs to track which jids are currently sending traffic to which component connection. At least for the non-disruptive thing you mentioned in comment 4

from jitsi-meet.

Not necessarily. If the bridge retrieves the items from the server, with different names but in a guaranteed order, that would be enough and would only require minor additions in JitMeet

from jitsi-meet.

Implemented in Jicofo.

from jitsi-meet.