ticdc: version 8.3.0 of TiCDC is not compatible with version 8.1.0 of TiKV #11507
Labels
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
type/bug
The issue is confirmed as a bug.
What did you do?
Description:
While performing integration testing with TiCDC's master branch (version 8.3.0), I encountered an issue where the
batch_add_table
test fails. The TiCDC node crashes because the puller module panics during DDL execution.Steps to Reproduce:
make prepare_test_binaries community=true
to download TiDB, TiKV, PD, and other components. This pulls version 8.1.0 of the components (I'll explain why below).make integration_test_build
.make integration_test
to start the integration test.Observed Behavior:
During the
batch_add_table
integration test, TiCDC's puller module panics when processing DDL, causing the TiCDC node to crash.Cause Analysis:
The reason TiCDC 8.3.0 pulled version 8.1.0 of TiDB, TiKV, PD, etc., is that when running
make prepare_test_binaries
with thecommunity=true
option, if the version is not manually specified, it defaults to downloading version 8.1.0 of all TiDB components. (related to #11508)After manually replacing the TiDB, TiKV, PD components with the latest versions, the
batch_add_table
integration test passed successfully. This indicates that TiCDC 8.3.0 currently does not maintain backward compatibility with TiKV 8.1.0.What did you expect to see?
I expected the batch_add_table integration test to pass without any issues when using TiCDC 8.3.0 with TiDB, TiKV, and PD components (even if they are from version 8.1.0). The system should handle version differences gracefully, or at the very least, the prepare_test_binaries step should automatically pull compatible versions of all components.
What did you see instead?
Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):8.1.0
Upstream TiKV version (execute
tikv-server --version
):8.1.0
TiCDC version (execute
cdc version
):8.3.0
The text was updated successfully, but these errors were encountered: