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
txn: use start_ts + 1 as Flush's min_commit_ts #16881
txn: use start_ts + 1 as Flush's min_commit_ts #16881
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Signed-off-by: ekexium <eke@fastmail.com>
db45471
to
bf8bd28
Compare
@@ -123,7 +123,8 @@ impl Flush { | |||
// txn_size is unknown, set it to max to avoid unexpected resolve_lock_lite | |||
txn_size: u64::MAX, | |||
lock_ttl: self.lock_ttl, | |||
min_commit_ts: TimeStamp::zero(), | |||
// min_commit_ts == 0 will disallow readers pushing it | |||
min_commit_ts: self.start_ts.next(), |
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.
Should the min_commit_ts
be passed from the Flush
kv request?
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.
It could be. But in current implementation we don't have to. We can change it in the future when needed.
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.
It's better to use the min_commit_ts
from the FlushRequest
I think, otherwise that field would always be coverd.
@@ -123,7 +123,8 @@ impl Flush { | |||
// txn_size is unknown, set it to max to avoid unexpected resolve_lock_lite | |||
txn_size: u64::MAX, | |||
lock_ttl: self.lock_ttl, | |||
min_commit_ts: TimeStamp::zero(), | |||
// min_commit_ts == 0 will disallow readers pushing it | |||
min_commit_ts: self.start_ts.next(), |
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.
It's better to use the min_commit_ts
from the FlushRequest
I think, otherwise that field would always be coverd.
/merge |
@ekexium: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests You only need to trigger
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
This pull request has been accepted and is ready to merge. Commit hash: bf8bd28
|
@ekexium: Your PR was out of date, I have automatically updated it for you. If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
close tikv#16880 The PR fixes the problem that locks written by pipelined-dml block reads. Now min_commit_ts was set to start_ts + 1 for Flush commands. Previously it was set to 0, which disallows pushing min_commit_ts. Signed-off-by: ekexium <eke@fastmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
In response to a cherrypick label: new pull request created to branch |
close #16880 The PR fixes the problem that locks written by pipelined-dml block reads. Now min_commit_ts was set to start_ts + 1 for Flush commands. Previously it was set to 0, which disallows pushing min_commit_ts. Signed-off-by: ekexium <eke@fastmail.com> Co-authored-by: ekexium <eke@fastmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
What is changed and how it works?
Issue Number: Close #16880
What's Changed:
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note