Add storage sink retry mechanism
Open
Nobody has claimed this yet.
severity/moderate
type/enhancement
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
- TiCDC should attempt retries when some storage write operations fail.
- Logs indicating retry attempts and backoff.
- Clear documentation of retry behavior (strategy, limits, error handling).
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 locating TiCDC's storage sink write paths and their existing error handling. Review current logging and documentation around sink failures, then define the retry strategy, backoff, limits, and error behavior. The work is done when failed writes retry as specified, attempts and backoff are logged, and the retry behavior is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100