syncer(dm): option for explicit auto-id-cache handling in create table DDLs

[michaelmdeng]

What problem does this PR solve?

Issue Number: close #12039

What is changed and how it works?

Adds a new auto-id-cache-size Syncer config. When set, DM incremental replication of new tables will update the create table statement w/ the corresponding auto-id-cache size. When unset (0 or default), the statement will be left as is.

syncers:
  <name>:
    auto-id-cache-size: 1 # This sets MySQL-compatiblity mode for new tables
    ...

...

I believe this change should not affect other DM components, including import for "full" or "all" mode, but would appreciate guidance here as well.

Check List

Tests

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

Questions

Will it cause performance regression or break compatibility?

No

Do you need to update user documentation, design documentation or monitoring documentation?

Yes, needs documentation on the new config setting and its purpose/usage.

Release note

Allow control of `AUTO_ID_CACHE` size when DM in incremental mode creates new tables

[ti-chi-bot]

Hi @michaelmdeng. 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-sigs/prow repository.

[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 lance6716, yudongusa for approval, ensuring that each of them provides their approval before proceeding. 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
• dm/config/OWNERS

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

[sre-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ michaelmdeng
❌ Michael Deng

---

Michael Deng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[lance6716]

/ok-to-test

[ti-chi-bot]

@michaelmdeng: 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	25bccc3	link	true	/test pull-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-sigs/prow repository. I understand the commands that are listed here.