[Bug] Message hole if `writeAndFlush` failed
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar.
### Version
master
### Minimal reproduce step

### What did you expect to see?
if write failed ,we should write again
### What did you see instead?
only do nothing, the message will be a unacked message ,but consumer never got it.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [X] I'm willing to submit a PR!
Contributor guide
Research direction
Use the reported writeAndFlush failure reproduction as the starting point. Trace how the failed write leaves the message unacked and determine where delivery stops; done means a failed write does not leave the message permanently unseen by its consumer, with coverage for the reproduced case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100