Reduce the latency when replicating the "add index" ddl to the downstream(tidb)

[nongfushanquan]

What did you do?

When an "ADD INDEX" DDL is executed at the upstream, TiCDC will execute this DDL SQL at the downstream (TiDB) and hold the following DMLs.

What did you expect to see?

The latency is increasing.

What did you see instead?

DML will not be blocked by this ddl and can continue to execute.

Versions of the cluster

master

[nongfushanquan]

/assign @asddongmen

[fubinzh]

/severity major

[nongfushanquan]

/type enhancement

[ti-chi-bot]

@nongfushanquan: The label(s) bug cannot be applied. These labels are supported: duplicate, bug-from-internal-test, bug-from-user, affects-5.3, affects-5.4, affects-6.0, affects-6.1, affects-6.2, affects-6.3, affects-6.4, affects-6.5, affects-6.6, affects-7.0, affects-7.1, affects-7.2, affects-7.3, may-affects-5.3, may-affects-5.4, may-affects-6.0, may-affects-6.1, may-affects-6.2, may-affects-6.3, may-affects-6.4, may-affects-6.5, may-affects-6.6, may-affects-7.0, may-affects-7.1, may-affects-7.2, may-affects-7.3, needs-cherry-pick-release-5.3, needs-cherry-pick-release-5.4, needs-cherry-pick-release-6.0, needs-cherry-pick-release-6.1, needs-cherry-pick-release-6.2, needs-cherry-pick-release-6.3, needs-cherry-pick-release-6.4, needs-cherry-pick-release-6.5, needs-cherry-pick-release-6.6, needs-cherry-pick-release-7.0, needs-cherry-pick-release-7.1, needs-cherry-pick-release-7.2, needs-cherry-pick-release-7.3, question, release-blocker, wontfix, require-LGT1, require-LGT3.

In response to this:

/remove-label bug

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 ti-community-infra/tichi repository.

[nongfushanquan]

/assign @sdojjy
/unassign @asddongmen

[nongfushanquan]

/remove-label may-affects-7.1
/label affects-7.1

[nongfushanquan]

/remove-label may-affects-6.5
/label affects-6.5