The ddl info sent from upstream is not expected after enable BDR which lead to cdc panic repeatedly

[Lily2025]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

1、BDR cluster
2、run sysbench
3、run ddl on upstream
4、kill ddl owner

2. What did you expect to see? (Required)

no panic

3. What did you see instead (Required)

cdc of downstream panic repeatedly which may caused by this

4. What is your TiDB version? (Required)

./tidb-server -V
Release Version: v8.5.0-alpha-292-gf0070f54ab
Edition: Community
Git Commit Hash: f0070f5
Git Branch: HEAD
UTC Build Time: 2024-12-05 13:06:31
GoVersion: go1.23.4
Race Enabled: false
Check Table Before Drop: false
Store: unistore
2024-12-05T22:15:52.276+0800

[Lily2025]

/severity major
/assign D3Hunter

[D3Hunter]

after checking MVCC of job 423 on done state, it's 0 because it's skipped for no such index

{
    "id": 423,
    "type": 8,
    "schema_id": 358,
    "table_id": 325,
    "schema_name": "sysbench_64_7000w",
    "table_name": "sbtest5",
    "state": 4,
    "warning": {
        "class": 2,
        "code": 1091,
        "message": "index index_test_1733409957430 doesn't exist",
        "rfccode": "ddl:1091"
    },
.....
    "schema_state": 5,
    "query": "ALTER TABLE `sbtest5` DROP INDEX IF EXISTS `index_test_1733409957430`",
    "binlog": {
        "SchemaVersion": 0,
        "DBInfo": null,

[D3Hunter]

not a bug, close

[D3Hunter]

refer #58049 too

[Lily2025]

cdc panic issue：pingcap/tiflow#11839