-
Notifications
You must be signed in to change notification settings - Fork 286
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
(redo)ticdc: fix the event orderliness in redo log #11117
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #11117 +/- ##
================================================
+ Coverage 57.5466% 57.6426% +0.0959%
================================================
Files 853 854 +1
Lines 125679 126266 +587
================================================
+ Hits 72324 72783 +459
- Misses 47986 48102 +116
- Partials 5369 5381 +12 |
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.
LGTM
cdc/redo/reader/reader.go
Outdated
h[i].data.RedoRow.Row.StartTs < h[j].data.RedoRow.Row.StartTs { | ||
return true | ||
if h[i].data.RedoRow.Row.CommitTs == h[j].data.RedoRow.Row.CommitTs { | ||
if h[i].data.RedoRow.Row.StartTs < h[j].data.RedoRow.Row.StartTs { |
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.
remove useless else branch:
if h[i].data.RedoRow.Row.StartTs < h[j].data.RedoRow.Row.StartTs { | |
if h[i].data.RedoRow.Row.StartTs != h[j].data.RedoRow.Row.StartTs { | |
return h[i].data.RedoRow.Row.StartTs < h[j].data.RedoRow.Row.StartTs | |
} | |
... |
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.
Good Point!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CharlesCheung96, lidezhu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest |
1 similar comment
/retest |
/retest |
1 similar comment
/retest |
/cherry-pick release-8.1 |
@hongyunyan: once the present PR merges, I will cherry-pick it on top of release-8.1 in the new PR and assign it to you. In 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. |
/test cdc-integration-kafka-test |
return h[i].data.RedoRow.Row.StartTs < h[j].data.RedoRow.Row.StartTs | ||
} | ||
// in the same txn, we need to sort by delete/update/insert order | ||
if h[i].data.RedoRow.Row.ToRowChangedEvent().IsDelete() { |
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.
ToRowChangedEvent
should only be called once, if it may cost some resource.
else
is redundant I think.
expect bool | ||
}{ | ||
{ | ||
name: "Delete before Update", |
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.
These data is hard to read, use schema test helper to new events is preferred.
I would suggest that test for each case independently, instead of create a tests
and loop over each.
@hongyunyan: new pull request created to branch In 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. |
In response to a cherrypick label: new pull request could not be created: failed to create pull request against pingcap/tiflow#release-8.1 from head ti-chi-bot:cherry-pick-11117-to-release-8.1: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-11117-to-release-8.1."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} |
/run-cherry-picker |
In response to a cherrypick label: new pull request created to branch |
/run-cherry-picker |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
commit c092599 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Wed Jun 12 00:26:59 2024 +0800 pkg/config, sink(ticdc): support output raw change event for mq and cloud storage sink (pingcap#11226) (pingcap#11290) close pingcap#11211 commit 3426e46 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Tue Jun 11 19:40:29 2024 +0800 puller(ticdc): fix wrong update splitting behavior after table scheduling (pingcap#11269) (pingcap#11282) close pingcap#11219 commit 2a28078 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Tue Jun 11 16:40:37 2024 +0800 mysql(ticdc): remove error filter when check isTiDB in backend init (pingcap#11214) (pingcap#11261) close pingcap#11213 commit 2425d54 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Tue Jun 11 16:40:30 2024 +0800 log(ticdc): Add more error query information to the returned error to facilitate users to know the cause of the failure (pingcap#10945) (pingcap#11257) close pingcap#11254 commit 053cdaf Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Tue Jun 11 15:34:30 2024 +0800 cdc: log slow conflict detect every 60s (pingcap#11251) (pingcap#11287) close pingcap#11271 commit 327ba7b Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Tue Jun 11 11:42:00 2024 +0800 redo(ticdc): return internal error in redo writer (pingcap#11011) (pingcap#11091) close pingcap#10124 commit d82ae89 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Mon Jun 10 22:28:29 2024 +0800 ddl_puller (ticdc): handle dorp pk/uk ddl correctly (pingcap#10965) (pingcap#10981) close pingcap#10890 commit f15bec9 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Fri Jun 7 16:16:28 2024 +0800 redo(ticdc): enable pprof and set memory limit for redo applier (pingcap#10904) (pingcap#10996) close pingcap#10900 commit ba50a0e Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Wed Jun 5 19:58:26 2024 +0800 test(ticdc): enable sequence test (pingcap#11023) (pingcap#11037) close pingcap#11015 commit 94b9897 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Wed Jun 5 17:08:56 2024 +0800 mounter(ticdc): timezone fill default value should also consider tz. (pingcap#10932) (pingcap#10946) close pingcap#10931 commit a912d33 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Wed Jun 5 10:49:25 2024 +0800 mysql (ticdc): Improve the performance of the mysql sink by refining the transaction event batching logic (pingcap#10466) (pingcap#11242) close pingcap#11241 commit 6277d9a Author: dongmen <20351731+asddongmen@users.noreply.github.com> Date: Wed May 29 20:13:22 2024 +0800 kvClient (ticdc): revert e5999e3 to remove useless metrics (pingcap#11184) close pingcap#11073 commit 54e93ed Author: dongmen <20351731+asddongmen@users.noreply.github.com> Date: Wed May 29 17:43:22 2024 +0800 syncpoint (ticdc): make syncpoint support base64 encoded password (pingcap#11162) close pingcap#10516 commit 0ba9329 Author: Ti Chi Robot <ti-community-prow-bot@tidb.io> Date: Wed May 29 09:07:21 2024 +0800 (redo)ticdc: fix the event orderliness in redo log (pingcap#11117) (pingcap#11180) close pingcap#11096 Signed-off-by: qupeng <qupeng@pingcap.com>
What problem does this PR solve?
Issue Number: close #11096
What is changed and how it works?
Check List
Tests
Unit test
Manual test (add detailed scripts or steps below)
create mysql sink changefeed with redo log on
run gotpc workload
After 30m, pause changefeed and run redo apply
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note