cdc: remove assertion on the lock start-ts#19084
cdc: remove assertion on the lock start-ts#19084ti-chi-bot[bot] merged 26 commits intotikv:masterfrom
Conversation
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
This reverts commit d99bd9b. Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
2f787b6 to
379ed43
Compare
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
|
/test pull-unit-test |
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
|
/test pull-unit-test |
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
|
@3AceShowHand |
|
/retest |
|
/test pull-unit-test |
Yes, I am investigating how to handle the |
Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
| assert_eq!(row.lock_count_modify, 0); | ||
| let start_ts = TimeStamp::from(row.v.start_ts); | ||
| row.lock_count_modify = self.pop_lock(key, start_ts)?; | ||
| let mut modified = self.pop_lock(key, start_ts)?; |
There was a problem hiding this comment.
This is a important change.
Previous code assert_eq!(row.lock_count_modify, 0); make one assumption that there is no 2 put request with the same key in the one batch.
The assertion is removed, and make that it is possible the case above happens. For example, lock cf put key a, and then write cf pop key a.
|
/retest |
cfzjywxk
left a comment
There was a problem hiding this comment.
LGTM, we may leave the lock cf handling compalitity refactor in the later PR
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfzjywxk, overvenus The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick release-8.5 |
close tikv#19083 Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
@3AceShowHand: new pull request created to branch DetailsIn response to this:
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 #19083 * revert #16864 to avoid the TiKV-CDC panic due to assertion failed Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> Signed-off-by: 3AceShowHand <jinl1037@hotmail.com> Co-authored-by: Ling Jin <7138436+3AceShowHand@users.noreply.github.com> Co-authored-by: 3AceShowHand <jinl1037@hotmail.com>
close tikv#19083 * revert tikv#16864 to avoid the TiKV-CDC panic due to assertion failed Signed-off-by: 3AceShowHand <jinl1037@hotmail.com>
What is changed and how it works?
Issue Number: Close #19083
What's Changed:
generationfield is removed by revert the PR, need to do more work about how to support pipelined DML.push_lock, just push it like before, and print logs if there is already the lock with the same key.Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note