Skip to content
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

puller(ticdc): always split update kv entries in sink safe mode (#11224) #11657

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #11224

What problem does this PR solve?

Issue Number: close #11231

What is changed and how it works?

After introduce #10919, we choose to just split some update kv entries in puller module when changefeed starts and avoid split any update events in sink module.
This makes it possible to meet duplicate entry error during normal run and cause changefeed to restart.
Although after restart, puller can split the conflict update events and changefeed can continue to run normally. Some customer may be unhappy with this behavior if their workload has many conflict data which cause changefeed restart occasionally. So we need a workaround to avoid restart.

This pr introduce a type PullerSplitUpdateMode to describe how puller handle update kv entries. We keep all split logic unchanged as in #10919, and introduce a new behaviour:
When mysql sink is in safe mode, we set PullerSplitUpdateMode to PullerSplitUpdateModeAlways. This means to split all update kv entries in puller. So if the customer don't want changefeed to restart, they can config safe-mode to true to avoid the restart.

Check List

Tests

  • Unit test
  • Manual test (add detailed scripts or steps below)

Questions

Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?

Release note

None

@ti-chi-bot ti-chi-bot added lgtm release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/cherry-pick-for-release-8.1 This PR is cherry-picked to release-8.1 from a source PR. labels Oct 12, 2024
@ti-chi-bot ti-chi-bot bot added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Oct 12, 2024
Copy link

codecov bot commented Oct 12, 2024

Codecov Report

Attention: Patch coverage is 46.96970% with 35 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@92c1bbd). Learn more about missing BASE report.

Additional details and impacted files
Components Coverage Δ
cdc 61.7975% <0.0000%> (?)
dm 51.0884% <0.0000%> (?)
engine 63.4091% <0.0000%> (?)
Flag Coverage Δ
unit 57.4254% <46.9697%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

@@               Coverage Diff                @@
##             release-8.1     #11657   +/-   ##
================================================
  Coverage               ?   57.4254%           
================================================
  Files                  ?        854           
  Lines                  ?     126033           
  Branches               ?          0           
================================================
  Hits                   ?      72375           
  Misses                 ?      48255           
  Partials               ?       5403           

@lidezhu
Copy link
Collaborator

lidezhu commented Oct 12, 2024

/retest

Copy link
Contributor

ti-chi-bot bot commented Oct 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Oct 12, 2024
@lidezhu
Copy link
Collaborator

lidezhu commented Oct 12, 2024

/test dm-integration-test

@lidezhu
Copy link
Collaborator

lidezhu commented Oct 12, 2024

/retest

1 similar comment
@lidezhu
Copy link
Collaborator

lidezhu commented Oct 12, 2024

/retest

@lidezhu
Copy link
Collaborator

lidezhu commented Oct 12, 2024

/test dm-integration-test

@ti-chi-bot ti-chi-bot bot merged commit c6bfe85 into pingcap:release-8.1 Oct 12, 2024
27 checks passed
@lidezhu lidezhu deleted the cherry-pick-11224-to-release-8.1 branch October 12, 2024 05:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. type/cherry-pick-for-release-8.1 This PR is cherry-picked to release-8.1 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants