Make rep's locket TTL configurable - #1180
Merged
Merged
Conversation
TNZ-123644 ai-assisted=yes
cf-foundation-community-automation
Bot
moved this to Inbox
in Application Runtime Platform Working Group
geofffranks
approved these changes
Jul 30, 2026
github-project-automation
Bot
moved this from Inbox
to Pending Merge | Prioritized
in Application Runtime Platform Working Group
github-project-automation
Bot
moved this from Pending Merge | Prioritized
to Done
in Application Runtime Platform Working Group
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
lock_ttl had been hardcoded to 15s and effectively the lock expires before keepalive time and timeout is reached (32s) by default. This will allow us to increase the lock_ttl to a bigger number like 45s, so that would allow the rep to keep its presence and convergence wouldn't kick off.
Backward Compatibility
Breaking Change? No