When set enable-table-across-nodes = true
and write-key-threshold
large than 0, there may be a risk of span loss, causing the changefeed stucks.
#11675
Labels
affects-6.5
affects-7.1
affects-7.5
affects-8.1
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
type/bug
The issue is confirmed as a bug.
What did you do?
What did you expect to see?
Changefeed does not stuck.
What did you see instead?
changefeed stuck and the log below was found:
After the split operation, the
end_key: 7480000000000000ff8a5f730000000000fa
never appeared in the logs; under normal circumstances, it should have been printed in the scheduler's logs (add table).Versions of the cluster
Upstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):(paste TiDB cluster version here)
Upstream TiKV version (execute
tikv-server --version
):(paste TiKV version here)
TiCDC version (execute
cdc version
):v7.5.3
The text was updated successfully, but these errors were encountered: