[GitHub] [pulsar] codelipenghui opened a new issue #5693: [documentation] Clarify the messages(data) be invisible

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

codelipenghui opened a new issue #5693: [documentation] Clarify the messages(data) be invisible
URL: https://github.com/apache/pulsar/issues/5693
 
 
   **Is your feature request related to a problem? Please describe.**
   If all subscriptions mark delete at a position, the messages before that position will be delete. Always, users understand the mechanism like send a message to the topic, and a new consumer A create a new subscription SUB-A with the earliest position and acknowledge the message, then a new consumer B also create a new subscription SUB-B with the earliest position, since consumer A already acknowledge the message, and at that time topic only have SUB-A subscription, so consumer B should not receive that message.
   
   But, actually the consumer B also can receive that message, because broker will not delete the current active ledger in the topic, data will be invisible to the user until the ledger rollover happens.
   
   So, here add an issue to track the documentation of how messages be invisible works.
   
   
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services