tests: Kafka split-table move case exhausts downstream DDL disk
@asddongmen is already working on this.
Since Sep 12, 2026.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What did you do?
Run Kafka-heavy G01 on master a62695e1, which includes the resource reduction from #6211.
Failed build: https://do.pingcap.net/jenkins/job/pingcap/job/ticdc/job/pull_cdc_kafka_integration_heavy/39/
What did you expect to see?
ddl_for_split_tables_with_random_move_table should finish and replicate the workload completion marker within the configured resource limit.
What did you see instead?
TiCDC sent CREATE TABLE test.workload_finished to Kafka, but the consumer was still retrying an earlier CREATE INDEX idx_data ON test.table_2 (data). Downstream TiDB returned error 8256 because /tmp/tidb/tmp_ddl-3306 had 19,031,883,776 bytes free while more than 19,145,797,632 bytes were required. The case then timed out waiting for the marker.
This is a follow-up to #6210/#6211: the reduced workload still leaves insufficient downstream DDL disk headroom in Kafka-heavy CI.
Versions of the cluster
TiCDC master at a62695e1b678137a41695199da826c261b8f7468.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.