Please answer these questions before submitting your issue. Thanks!

1. What did you do?
   If possible, provide a recipe for reproducing the error.
   When cdc outputs the ddl operation, name the suffix of the ddl file name as uint64max-TS of the first ddl operation (it can be directly named as the TS of the last ddl), and then when collecting ddl files during br recovery, add this ts is regarded as the TS of the last ddl, and all ddl smaller than startTs are filtered out, so some ddl files that should not be filtered are filtered out, so some ddl operations are not restored when they are restored.

2. What did you expect to see?

3. What did you see instead?

4. What version of BR and TiDB/TiKV/PD are you using?

5. Operation logs

   • Please upload br.log for BR if possible
   • Please upload tidb-lightning.log for TiDB-Lightning if possible
   • Please upload tikv-importer.log from TiKV-Importer if possible
   • Other interesting logs

6. Configuration of the cluster and the task

   • tidb-lightning.toml for TiDB-Lightning if possible
   • tikv-importer.toml for TiKV-Importer if possible
   • topology.yml if deployed by TiUP

7. Screenshot/exported-PDF of Grafana dashboard or metrics' graph in Prometheus if possible