ticdc v5.3.0

Improvements

• Reduce the default value of the Kafka sink configuration item MaxMessageBytes from 64 MB to 1 MB to fix the issue that large messages are rejected by the Kafka Broker #3104
• Reduce memory usage in the replication pipeline #2553#3037 #2726
• Optimize monitoring items and alert rules to improve observability of synchronous links, memory GC, and stock data scanning processes #2735 #1606 #3000 #2985 #2156
• When the sync task status is normal, no more historical error messages are displayed to avoid misleading users #2242

Bug Fixes

• Fix the issue that TiCDC replication task might terminate when the upstream TiDB instance unexpectedly exits #3061
• Fix the issue that TiCDC process might panic when TiKV sends duplicate requests to the same Region #2386
• Fix unnecessary CPU consumption when verifying downstream TiDB/MySQL availability #3073
• Fix the issue that the volume of Kafka messages generated by TiCDC is not constrained by max-message-size #2962
• Fix the issue that TiCDC sync task might pause when an error occurs during writing a Kafka message #2978
• Fix the issue that some partitioned tables without valid indexes might be ignored when force-replicate is enabled #2834
• Fix the issue that scanning stock data might fail due to TiKV performing GC when scanning stock data takes too long #2470
• Fix a possible panic issue when encoding some types of columns into Open Protocol format #2758
• Fix a possible panic issue when encoding some types of columns into Avro format #2648