[GitHub] [pulsar] eolivelli edited a comment on issue #11002: [Transactions] Pulsar Admin: peekMessages is returning a wrong message, dealing with non empty list of individuallyDeletedMessages

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

eolivelli edited a comment on issue #11002:
URL: https://github.com/apache/pulsar/issues/11002#issuecomment-866874062


   I am continuing my investigation and it looks like when I send messages using a transaction the 'commit' operation uses a messageId.
   
   So:
   - create transaction 1
   - send message using transaction 1, message id is for instance `3:0:-1:0`
   - commit transaction 1
   - create transaction 2
   - send message using transaction 2, message id is for instance `3:2:-1:0`
   - commit transaction 2
   
   so message 3:1:-1 does not exist, and when a consumer tried to acknowledge the messages the subscriptions ends up in this state in which there are systematically holes and the `individuallyDeletedMessages` keeps growing and `peekMessages` is not able to report the correct value.
   
   I am trying to create a reproducer as a test case in current Pulsar master branch
    
   
   


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