kafka sink report in.sync.replicas not enough cause the whole changefeed failed and then checkpoint lag increase a lot
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
The changefeed set replication-factor as 3, and min.insync.replicas = 3, It means that the message need to be acked by 3 replicas.
Sometime, Kafka sink report errors like fewer in-sync replicas than required, it makes the whole changefeed failed, but we should can retry in the such case.
Solution
Report error to the upper level, do not restart the whole changefeed, but only a part of the whole changefeed, to reduce the affect area.
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 at the Kafka sink handling of the fewer in-sync replicas than required error and trace how that error reaches the changefeed restart path. Confirm the retry behavior and affected scope described in the solution, with completion shown by preventing the whole changefeed from failing and avoiding unnecessary checkpoint lag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100