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.

Sign up for GitHub

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

Jump to bottom

[CHA-RL7] Room lifecycle operation precendence #34

Open

sacOO7 opened this issue Oct 23, 2024 · 0 comments

Assignees

sacOO7 commented Oct 23, 2024 •

edited

Loading

This is an important part of room lifecycle management.
Spec states that
(CHA-RL7a) [Testable] Room lifecycle operations have a precedence. If multiple operations are scheduled to run, they run in the following order:
(CHA-RL7a1) The RETRY operation – an internal process.
(CHA-RL7a2) The RELEASE operation.
(CHA-RL7a3) The ATTACH and DETACH operations have equal precedence
We have currently specified two solutions for this

I have listed few concerns with option 1, since it needs extra implementation to handle edge cases and can cause memory leaks even after room release.
So, currently going with option 2, I have raised channel attach PR on top of it -> [ECO-5009][CHA-RL1] Roomlifecycle Attach with retry #33. We can refactor it a bit more, but I strongly believe the current impl. is well-tested and can be used as a part of the room lifecycle

┆Issue is synchronized with this Jira Task by Unito

sacOO7 self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment