After stopping the bookie and recovering, it can be produced at this time, but cannot be consumed normally. Restarting the broker can resume normal #5962
Labels
type/bug
The PR fixed a bug or issue reported a bug
Comments
|
thanks @liudezhi2098 for helping this this issue |
jiazhai
pushed a commit
that referenced
this issue
Jan 3, 2020
…e entire bookie is restored, it can be produced at this time, and the produced data cannot be consumed normally. Restarting the broker can resume normal (#5965) After stopping the bookie and recovering, it can be produced at this time, but cannot be consumed normally. Restarting the broker can resume normal Fixes #5962 Motivation problem : Topic(E=3,W=3,A=2), stopped 2 bookie nodes, then recover the 2 bookie, The message can be produced normally, but the consumer cannot pull the message unless the broker is restarted. We hope that the bookie summary will resume normal consumption Modifications The main cause of this problem is that readHandle.readAsync does not catch the exception, causing some methods to not trigger. therefore, added the exception capture module , and the exceptions involved in the bookeeper project are also fixed.
huangdx0726
pushed a commit
to huangdx0726/pulsar
that referenced
this issue
Aug 24, 2020
…e entire bookie is restored, it can be produced at this time, and the produced data cannot be consumed normally. Restarting the broker can resume normal (apache#5965) After stopping the bookie and recovering, it can be produced at this time, but cannot be consumed normally. Restarting the broker can resume normal Fixes apache#5962 Motivation problem : Topic(E=3,W=3,A=2), stopped 2 bookie nodes, then recover the 2 bookie, The message can be produced normally, but the consumer cannot pull the message unless the broker is restarted. We hope that the bookie summary will resume normal consumption Modifications The main cause of this problem is that readHandle.readAsync does not catch the exception, causing some methods to not trigger. therefore, added the exception capture module , and the exceptions involved in the bookeeper project are also fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Topic(E=3,W=3,A=2), stopped 2 bookie nodes, then recover the 2 bookie,
The message can be produced normally, but the consumer cannot pull the message unless the broker is restarted.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: