poorbarcode commented on PR #23803:
URL: https://github.com/apache/pulsar/pull/23803#issuecomment-2611397108

   @lhotari 
   
   BTW, we can start a new email channel to talk about this.
   
   >> It may lead E2E latency increases
   > There would be an opposite impact when handled correctly. 
   
   I consider that the current implementation is the best solution
   
   >> The pending normal read will be looped to set and cancel
   >> It may be a conflict with the feature read ahead before all messages sent 
are acknowledged
   > Please explain more about these items since I didn't catch the meaning.
   
   The case Read Ahead:
   - there is consumer stuck, which leads messages being pushed into 
redeliver-queue
   - there is consumer not stuck, which need to read new messages
   
   I think we should not cancel `pending normal read`.


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