Changefeed checkpoint cannot proceed In massive inserts scenario
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
What did you do?
CDC sync to gcs scenario
CREATE TABLE amazon_review (
review_date int DEFAULT NULL,
marketplace varchar(20) DEFAULT NULL,
customer_id bigint DEFAULT NULL,
review_id varchar(40) DEFAULT NULL,
product_id varchar(20) DEFAULT NULL,
product_parent bigint DEFAULT NULL,
product_title varchar(500) DEFAULT NULL,
product_category varchar(50) DEFAULT NULL,
star_rating int DEFAULT NULL,
helpful_votes int DEFAULT NULL,
total_votes int DEFAULT NULL,
vine tinyint(1) DEFAULT NULL,
verified_purchase tinyint(1) DEFAULT NULL,
review_headline varchar(500) DEFAULT NULL,
review_body text DEFAULT NULL,
id bigint NOT NULL AUTO_INCREMENT,
PRIMARY KEY (id) /*T![clustered_index] CLUSTERED */
)
ks3://fts/amazon_review_csv.tar.gz( from ks3)
Execute multiple times in succession lighting import using tidb backend
What did you expect to see?
Data can be synchronized normally.
What did you see instead?
Several hours after the write stopped, the changefeed checkpoint could not proceed normally, and the S3 write was interrupted.
Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
Edition: Community
Git Commit Hash: 55de6a498a4da495cac4893e05386754cae51b9e
Git Branch: HEAD
UTC Build Time: 2026-02-11 14:56:14
GoVersion: go1.25.5
Race Enabled: false
Check Table Before Drop: false
Store: unistore
Kernel Type: Classic
Upstream TiKV version (execute tikv-server --version):
TiKV
Release Version: 9.0.0-beta.2
Edition: Community
Git Commit Hash: b1028c06d08b5859f0b09cbe8c312c4782ae85b9
Git Commit Branch: HEAD
UTC Build Time: 2026-02-06 05:24:44
Rust Version: rustc 1.87.0-nightly (96cfc7558 2025-02-27)
Enable Features: memory-engine pprof-fp jemalloc mem-profiling portable sse test-engine-kv-rocksdb test-engine-raft-raft-engine trace-async-tasks openssl-vendored
Profile: dist_release
TiCDC version (execute cdc version):
Release Version: v8.5.4-nextgen.202510.5-69-gc20a19d
Git Commit Hash: c20a19da6150b60548a2877a18fcbfea90ba40b6
Git Branch: HEAD
UTC Build Time: 2026-02-11 17:20:00
Go Version: go version go1.25.5 linux/amd64
Failpoint Build: false
Kernel Type: Classic
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.
Research direction
No source file or test is named. Start by reproducing the CDC sync to GCS while running repeated massive imports, then inspect the changefeed checkpoint and interrupted object-storage write behavior using the supplied TiDB, TiKV, and TiCDC versions. Done means the checkpoint advances normally and synchronization completes after the writes stop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud
- Domain
- data-engineering, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100