ddl: record get owner TS and compare it before runReorgJob quit

[tangenta]

What problem does this PR solve?

Issue Number: close #54897

Problem Summary:

Timeline:

1. tidb-0 run ingest backfill workers as the DDL owner.
2. Inject network latency to tidb-0.
3. tidb-1 get DDL owner, and switch to merge temp index step.
4. Inject network latency to tidb-1. tidb-1's merge temp index backfill workers failed with "DDL is not owner"
5. tidb-0 get DDL owner AGAIN, but reorgCtx is the one added in step(1).
6. Merge temp index step is skipped because the reorgCtx is done.

What changed and how does it work?

Record get owner TS and compare it before runReorgJob quit.

Check List

Tests

• Unit test
• Integration test
  Here is the log from HA test:
  
• Manual test (add detailed scripts or steps below)
• 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

Attention: Patch coverage is 69.56522% with 7 lines in your changes missing coverage. Please review.

Project coverage is 75.3087%. Comparing base (199bf90) to head (44e93b0).
Report is 663 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55049        +/-   ##
================================================
+ Coverage   72.6158%   75.3087%   +2.6928%     
================================================
  Files          1565       1565                
  Lines        440229     442634      +2405     
================================================
+ Hits         319676     333342     +13666     
+ Misses       100711      88593     -12118     
- Partials      19842      20699       +857     

Flag	Coverage Δ
integration	51.1158% <69.5652%> (?)
unit	71.6708% <69.5652%> (+0.0071%)	⬆️

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

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

[tangenta]

/hold

[tangenta]

/unhold

[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.

[D3Hunter]

we should reset reorgCtx on owner change, to avoid read stale data, but ok as a quick fix

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, 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:

• pkg/ddl/OWNERS [wjhuang2016]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-07-31 09:44:16.31353408 +0000 UTC m=+348972.593582150: ☑️ agreed by wjhuang2016.
• 2024-07-31 10:18:56.351621885 +0000 UTC m=+351052.631669953: ☑️ agreed by D3Hunter.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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