-
Notifications
You must be signed in to change notification settings - Fork 233
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
Support adaptive update interval for low resolution ts #1484
Merged
ti-chi-bot
merged 12 commits into
tikv:master
from
MyonKeminta:m/adaptive-low-resolution-tso-update-interval
Nov 11, 2024
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
590500a
Draft implementation
MyonKeminta 6979a6d
Refine interactions between goroutines; add logs
MyonKeminta 5a322d8
Add tests
MyonKeminta 59d5568
Cover configuration changes
MyonKeminta 19c6546
Add more tests
MyonKeminta 5a945e9
fix lint
MyonKeminta 7e9bae9
fix lint
MyonKeminta aea7b19
Adderss comments
MyonKeminta 96c6007
clear the code of nextInterval
MyonKeminta 0e9c8b8
Address comments
MyonKeminta 2fef49a
Add metrics
MyonKeminta 385419d
Adjust comments
MyonKeminta File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about deprecating the usages of this interface in the future, or integrate the check of
ValidateSnapshotReadTS
into it?It's more robust to return a verifed timestamp.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've considered this. It makes sence, but it can't be easily done due to the current usage in TiDB repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we modify
GetStaleTimestamp
to return the latest fetched timestamp, without adding the arrival duration?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussion with @MyonKeminta , the refactor done could be done in another PR as it requires a lot of work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What you said is exactly what
GetLowResolutionTSO
does. If we deprecate theGetStaleTimestamp
method, the change can be complictated and difficult considering the current usage in TiDB repo. Simply changing all usages ofGetStaleTimestamp
toGetLowResolutionTSO
may significantly reduce the precision of user specified staleness.