[GitHub] [pulsar] wenbingshen commented on issue #14559: Ignoring flow control message when resetCursorInProgress=TRUE

[GitBox <gi...@apache.org>]

wenbingshen commented on issue #14559:
URL: https://github.com/apache/pulsar/issues/14559#issuecomment-1060188329


   > It will be better for others to understand this if you can emphasize which step is not expected and what final result you got.
   
   Thanks for your replay. My expected result is: when my application finishes the seek operation, the first message read next must be the message where I seek.
   
   But now unfortunately, in my cluster, before the seek operation is completed, the broker has started to read the data starting from the current position from the bookie, and after my seek operation is completed, this part of the data is returned to the client , but the client does not want to know whether the position of the data it reads matches where it seeks, because the client has only two steps: 1. Execute seek, 2. Read the data immediately after the seek is completed.
   
   As shown in the figure below: The most important thing is to ensure the order of `5` and `6`. It should be executed first for `5`. The existing logic cannot guarantee this.
   
   ![image](https://user-images.githubusercontent.com/35599757/156968634-f7fbcac6-a64a-415f-960b-7ba53a58f066.png)
   
   


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org