Skip to content

Expose keep alive event configurarion in ec config and update defaults. #3303

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.

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

Merged
merged 8 commits into from
Jun 10, 2025

Conversation

toger5
Copy link
Contributor

@toger5 toger5 commented May 30, 2025

No description provided.

Copy link
Contributor

@fkwp fkwp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Comment on lines 121 to 122
* How long (in milliseconds) after the last keep-alive the server should expire the
* MatrixRTC membership event.
Copy link
Contributor

@fkwp fkwp Jun 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* How long (in milliseconds) after the last keep-alive the server should expire the
* MatrixRTC membership event.
* The duration (in milliseconds) after the most recent keep-alive (delayed leave event restart)
* that the server waits before emitting the expire MatrixRTC membership event.

key_rotation_on_leave_delay: 15000,
membership_keep_alive_period: 5000,
membership_server_side_expiry_timeout: 15000,
wait_for_key_rotation_ms: 5000,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this also be 3000 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know. In general the larger the better the experience. So probably 5000 is fine. Even though the example proposes a smaller value. (but then the sample is just the example and we wont always update it if we tune this part so them diverging is not an issue I think)

@toger5 toger5 merged commit 1425de8 into livekit Jun 10, 2025
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants