Make MySQL binlog staleness threshold configurable#4453
Merged
Conversation
ilidemi
changed the title
ilidemi
marked this pull request as ready for review
July 3, 2026 02:23
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
dtunikov
approved these changes
Jul 3, 2026
ilidemi
enabled auto-merge (squash)
July 7, 2026 01:09
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.
When the connection is slow, we can be taking a while to fully receive a new event for legitimate reasons. It is unlikely to happen (3 minutes at usual 20MB/s is 3.6GB and max binlog event is 1GB) but if it does, good to have a knob. Value is cached in env so catalog won't be hammered.
Resolves DBI-827