Page MenuHomePhorge

Support for multiple KMS instances with selection by current load
ClosedPublic

Authored by mollekopf on Jan 12 2021, 8:28 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 12, 5:03 PM
Unknown Object (File)
Sun, Mar 10, 9:06 AM
Unknown Object (File)
Sat, Mar 2, 12:37 AM
Unknown Object (File)
Feb 24 2024, 9:19 PM
Unknown Object (File)
Feb 23 2024, 7:05 AM
Unknown Object (File)
Feb 14 2024, 5:45 PM
Unknown Object (File)
Jan 29 2024, 6:50 PM
Unknown Object (File)
Jan 19 2024, 6:54 AM
Subscribers
None

Details

Summary

The load is simply the current number of webrtc connections.
This has mostly been based on removed code from
883d686542f2c72c86b8365978cadf2b13d315e4 and
e400a90942f7dcc160ab45ef0272157774dc59c5.

Verified that with two KMS instaces and two rooms, each get's used
once.
Look for "KMS less loaded is ws://localhost:8889/kurento with a load of
0.0" in the logs.

Diff Detail

Branch
dev/multikms
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 32629
Build 12595: arc lint + arc unit

Event Timeline

mollekopf created this revision.
  • no longer fails if some kms is initially unreachable
  • allowMoreElements is now taken into account

Alternatively we could also get rid of allowMoreElements if we don't need a limit on number of pipelines.

For the branch I would propose we base ourselves on the v2.16.0 tag

This revision is now accepted and ready to land.Jan 26 2021, 11:16 AM
This revision was automatically updated to reflect the committed changes.