All Recorders Busy Jibri


My Devops team has been trying to figure out this issue for a few weeks with no success. We always make 1.5X the number of Jibris available then we need, but even still users often report getting “All recorders busy” error. If only one meeting is doing recordings there is no problem, but as soon as it’s more than 1, we get the error. We have made each Jibri instance t2.2xlarge which seems absurdly large for the use and that seems to help, but doesn’t totally fix the problem. If there is a dev with a solution to better cycle through available Jibris, we would gladly pay for the fix. Please feel free to comment with your contact info. Thank you and have a great day.

Has each Jibri instance a unique nickname?