Commit f2e2f594 authored by pedrolab's avatar pedrolab

jitsi meet: clarify multiple jvbs instances

parent 036dd914
......@@ -35,7 +35,7 @@ and restart jicofo
Read if you are interested on knowing why this option is recommended
[As said by a jitsi developer](https://github.com/jitsi/jitsi-meet/issues/2172#issuecomment-389589242) health checks are for environments with multiple jvbs instances; in other words, there is no sense to have the health check for a single jvb instance. [The problem](https://github.com/jitsi/jitsi-meet/issues/2172) (at least with a single jvb instance) is that the healthcheck opens supposedly too much UDP ports that are not immediately closed after the healtcheck, hence, jicofo crashes and "jitsi is not working"
[As said by a jitsi developer](https://github.com/jitsi/jitsi-meet/issues/2172#issuecomment-389589242) health checks are for environments with multiple jvbs instances (this is the scenario of meet.jit.si, with multiple instances around the world attending the same service); in other words, there is no sense to have the health check for a single jvb instance. [The problem](https://github.com/jitsi/jitsi-meet/issues/2172) (at least with a single jvb instance) is that the healthcheck opens supposedly too much UDP ports that are not immediately closed after the healtcheck, hence, jicofo crashes and "jitsi is not working"
# Disable third party stuff
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment