create changefeed takes too much on verify tables
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
[2025/10/20 19:33:34.171 +08:00] [INFO] [changefeed.go:1481] ["verifyTables completed"] [tableCount=1] [startTs=461625041546641410]
[2025/10/20 19:33:34.171 +08:00] [INFO] [changefeed.go:395] ["verify table"] [forceReplicate=true] [ignoreIneligibleTable=false]
[2025/10/20 19:33:34.171 +08:00] [INFO] [middleware.go:87] ["cdc open api request"] [status=200] [method=POST] [path=/api/v2/verify_table] [query="keyspace=keyspace1"] [ip=10.234.156.73] [user-agent=Go-http-client/1.1] [client-version=v9.0.0-snapshot] [username=] [] [duration=3m50.433016226s]
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
Start with the verify_table request in middleware.go:87 and trace the related paths in changefeed.go:395 and changefeed.go:1481. Reproduce the create-changefeed operation while measuring the 3m50s duration, then identify why table verification takes so long. Done means the cause is addressed and the verification duration is demonstrably reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100