ticdc report receive untracked region resolved-ts
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?
the upstream is the special tikv-cdc
What did you expect to see?
nothing abnormal
What did you see instead?
[2025/08/18 14:11:38.624 +00:00] [WARN] [region_request_worker.go:307] ["region request worker receives a resolved ts event for an untracked region"] [workerID=5] [subscriptionID=3] [regionID=273] [resolvedTs=460200686017052673]
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):
master
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 by inspecting region_request_worker.go at line 307 and determine the conditions that produce the warning for an untracked region. Reproduce or investigate the report with complete TiDB, TiKV, and TiCDC version information; done means identifying why the resolved-ts event is received for the untracked region and documenting or correcting the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100