apache / apache/pulsar

support retry strategy when produce message

Open
#16,151 3 comments 0 reactions 0 assignees View on GitHub
Stale type/feature
Dominant language
Java
Stars
15.3k
Forks
3.8k
Avg merge
1d 14h
Merged PRs (30d)
160

Description

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

when we restart broker, client will sometimes fail, but if we support retry internal , they will retry to next partition in another broker (maybe ) will improve the success rate.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Java producer path used when a broker is restarted and a message send fails, then review how partition selection and failures are currently handled. Clarify whether retrying another partition is valid, define retry limits and failure behavior, and add tests showing the intended success and exhaustion cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.