poorbarcode opened a new pull request, #20335:
URL: https://github.com/apache/pulsar/pull/20335

   ### Motivation
   - https://github.com/apache/pulsar/pull/7105 provide a mechanism to avoid a 
stuck consumer affecting the consumption of other consumers: 
     - if all consumers can not accept more messages, stop delivering messages 
to the client.
     - if one consumer can not accept more messages, just read new messages and 
deliver them to other consumers.
   - https://github.com/apache/pulsar/pull/7553 provide a mechanism to fix the 
issue of lost order of consumption: If the consumer cannot accept any more 
messages, skip the consumer for the next round of message delivery because 
there may be messages with the same key in the replay queue.
   - https://github.com/apache/pulsar/pull/10762 provide a mechanism to fix the 
issue of lost order of consumption: If there have any messages with the same 
key in the replay queue, do not deliver the new messages to this consumer.
   
   https://github.com/apache/pulsar/pull/10762 and 
https://github.com/apache/pulsar/pull/7553 do the same thing and 
https://github.com/apache/pulsar/pull/10762 is better than 
https://github.com/apache/pulsar/pull/7553 , so 
https://github.com/apache/pulsar/pull/7553 is unnecessary. 
   
   ### Modifications
   remove the mechanism provided by https://github.com/apache/pulsar/pull/7553 
to avoid unnecessary consumption stuck.
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   
   ### Matching PR in forked repository
   
   PR in forked repository: 
   - x


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to