-
Notifications
You must be signed in to change notification settings - Fork 287
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
Data loss when upstream transcation conflicts during incremental scan #5468
Labels
affects-4.0
affects-5.0
affects-5.1
affects-5.2
affects-5.3
affects-5.4
affects-6.0
affects-6.1
area/ticdc
Issues or PRs related to TiCDC.
component/kv-client
TiKV kv log client component.
severity/critical
type/bug
The issue is confirmed as a bug.
Comments
overvenus
added
type/bug
The issue is confirmed as a bug.
component/kv-client
TiKV kv log client component.
severity/critical
area/ticdc
Issues or PRs related to TiCDC.
affects-5.3
affects-5.2
affects-5.1
affects-5.0
affects-4.0
affects-5.4
affects-6.0
affects-6.1
labels
May 18, 2022
12 tasks
12 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
May 23, 2022
This was referenced May 23, 2022
overvenus
added a commit
to overvenus/ticdc
that referenced
this issue
May 25, 2022
ti-chi-bot
added a commit
that referenced
this issue
May 25, 2022
overvenus
added a commit
that referenced
this issue
May 26, 2022
overvenus
added a commit
to overvenus/ticdc
that referenced
this issue
Jun 10, 2022
overvenus
added a commit
that referenced
this issue
Jun 13, 2022
/assign overvenus |
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 19, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Jun 20, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 21, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Jun 23, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Jun 23, 2022
overvenus
added a commit
to ti-chi-bot/tiflow
that referenced
this issue
Dec 9, 2022
…gcap#5477) close pingcap#5468 Signed-off-by: Neil Shen <overvenus@gmail.com>
ti-chi-bot
added a commit
that referenced
this issue
Dec 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-4.0
affects-5.0
affects-5.1
affects-5.2
affects-5.3
affects-5.4
affects-6.0
affects-6.1
area/ticdc
Issues or PRs related to TiCDC.
component/kv-client
TiKV kv log client component.
severity/critical
type/bug
The issue is confirmed as a bug.
What did you do?
For UPDATE SQL, its prewrite event has both value and old value.
It is possible that TiDB prewrites multiple times for the same row when
there are other transcations it conflicts with. For this case,
if the value is not "short", only the first prewrite contains the value.
TiKV may output events for the UPDATE SQL as following:
TiCDC mistakely outputs an event that contains the old value but not contains the value.
The event is translated into DELETE in sink, so the row is lost.
See line L718-L743
tiflow/cdc/kv/region_worker.go
Lines 718 to 743 in d76503b
What did you expect to see?
No data loss
What did you see instead?
Data is lost.
Versions of the cluster
TiCDC version (execute
cdc version
):v5.0.1
The text was updated successfully, but these errors were encountered: