checker(dm): update gtidSet by checkpoint data in MetaPositionChecker

[fishiu]

What problem does this PR solve?

Issue Number: close #11648

What is changed and how it works?

In MetaPositionChecker (GTID enabled), we used to compare only the GTID from config file with the upstream binlog. However when we restart with the same config, the GTID info from config might be outdated (e.g. old binlogs are purgeded), while the updated one is saved in checkpoint.

Now in MetaPositionChecker stage, we load checkpoint data from downstream db, and replace the GTID from config if it is outdated.

Check List

Tests

• Unit test

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign d3hunter for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• dm/OWNERS

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]

Hi @fishiu. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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/test-infra repository.

[lance6716]

/ok-to-test

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 16 lines in your changes missing coverage. Please review.

Project coverage is 55.1497%. Comparing base (62d07b5) to head (2d1bdd4).
Report is 1 commits behind head on master.

Additional details and impacted files

Components	Coverage Δ
cdc	59.6317% <ø> (-0.1970%)	⬇️
dm	50.0510% <0.0000%> (-0.0030%)	⬇️
engine	53.1997% <ø> (-0.0339%)	⬇️

Flag	Coverage Δ
unit	55.1497% <0.0000%> (-0.0945%)	⬇️

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

@@               Coverage Diff                @@
##             master     #11668        +/-   ##
================================================
- Coverage   55.2441%   55.1497%   -0.0945%     
================================================
  Files          1001       1001                
  Lines        136237     136483       +246     
================================================
+ Hits          75263      75270         +7     
- Misses        55486      55704       +218     
- Partials       5488       5509        +21     

[fishiu]

/retest

[fishiu]

/retest

[fishiu]

/retest

[fishiu]

/retest

[ti-chi-bot]

@fishiu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-dm-integration-test	2d1bdd4	link	true	/test dm-integration-test

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.