liudezhi2098 opened a new pull request #5965: fix  2 copies of 3bookie and stop 
2 booksie after production. After t…
URL: https://github.com/apache/pulsar/pull/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
   
   <!--
   ### Contribution Checklist
     
     - Name the pull request in the form "[Issue 5962][component] Title of the 
pull request", where *5962* should be replaced by the actual issue number.
       Skip *Issue 5962* if there is no associated github issue for this pull 
request.
       Skip *component* if you are unsure about which is the best component. 
E.g. `[docs] Fix typo in produce method`.
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
     
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
     
     - Each commit in the pull request has a meaningful commit message
   
     - Once all items of the checklist are addressed, remove the above text and 
this checklist, leaving only the filled out template below.
   
   **(The sections below can be removed for hotfixes of typos)**
   -->
   
   
   
   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.*
   
   
   
   
   
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to