keep resolved ts lag at a reasonable level during tikv rolling restart when there is a large number of regions
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
This issue has no description.
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
The issue provides no files, tests, reproduction steps, or target threshold. Start by tracing how TiCDC handles TiKV rolling restarts and resolved timestamps with many regions; clarify the acceptable lag and expected behavior with maintainers before identifying an implementation entry point or completion test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100