ddl/ingest: set minCommitTS when detect remote duplicate keys

[tangenta]

What problem does this PR solve?

Issue Number: close #55587

Problem Summary:

#55587 (comment)

What changed and how does it work?

Set minCommitTS when detect remote duplicate keys

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
  After this PR:

  mysql> set @@global.tidb_gc_life_time = '100m';
  Query OK, 0 rows affected (0.01 sec)
  
  mysql> drop table if exists t;
  Query OK, 0 rows affected, 1 warning (0.00 sec)
  
  mysql> create table t (a int, b int);
  Query OK, 0 rows affected (0.10 sec)
  
  mysql> insert into t values (1, 1);
  Query OK, 1 row affected (0.01 sec)
  
  mysql> select now();
  +---------------------+
  | now()               |
  +---------------------+
  | 2024-09-05 17:31:47 |
  +---------------------+
  1 row in set (0.00 sec)
  
  mysql> alter table t add index idx(b);
  Query OK, 0 rows affected (2.20 sec)
  
  mysql> flashback cluster to timestamp '2024-09-05 17:31:47';
  Query OK, 0 rows affected (2.22 sec)
  
  mysql> alter table t add unique index idx(b);
  Query OK, 0 rows affected (2.24 sec)

  Because using flashback cluster in real tikv test is very unstable, I test it manually. There is also an integration test on endless.
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @tangenta. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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 kubernetes-sigs/prow repository.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.9702%. Comparing base (e9124dd) to head (268c8f5).
Report is 125 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #55588         +/-   ##
=================================================
- Coverage   72.8514%   56.9702%   -15.8813%     
=================================================
  Files          1601       1759        +158     
  Lines        445302     642911     +197609     
=================================================
+ Hits         324409     366268      +41859     
- Misses       100894     251594     +150700     
- Partials      19999      25049       +5050     

Flag	Coverage Δ
integration	39.4882% <94.4444%> (?)
unit	71.9995% <33.3333%> (+0.0382%)	⬆️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (ø)
parser	∅ <ø> (∅)
br	62.3995% <ø> (+16.6228%)	⬆️

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-09-03 04:32:41.769139665 +0000 UTC m=+332486.287192582: ☑️ agreed by lance6716.
• 2024-09-03 05:50:06.393900488 +0000 UTC m=+337130.911953413: ☑️ agreed by wjhuang2016.

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

[lance6716]

/retest

[tiprow]

@lance6716: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, wjhuang2016

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:

• OWNERS [lance6716,wjhuang2016]
• pkg/ddl/OWNERS [lance6716,wjhuang2016]
• pkg/lightning/OWNERS [lance6716]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tangenta]

/retest

[tiprow]

@tangenta: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

[tangenta]

/retest

[tiprow]

@tangenta: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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 kubernetes-sigs/prow repository.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #56262.