Negative acknowledgement number of retries
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 142
Description
**Is your feature request related to a problem? Please describe.**
In actual use, if it still fails after a certain number of retries, put it in a dead letter. At present, if the dead letter queue is not configured, it seems that it will always try again. If a cancel confirmation is configured, it will be put into the dead letter.
**Describe the solution you'd like**
The number of retries can be configured.
**Describe alternatives you've considered**
Refer to other MQ retry strategies and dead letter strategies.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
The issue does not name any files, tests, or entry points. Start by tracing Pulsar's retry and dead-letter handling, then define how a configurable retry count should behave when no dead-letter queue or cancel confirmation is configured; done means the retry limit is configurable and failed messages follow the intended dead-letter behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100