[GitHub] [pulsar] wolfstudy commented on issue #19077: [Bug] MarkDeletePosition causes the corresponding ledger to not be deleted in borderline cases

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

wolfstudy commented on issue #19077:
URL: https://github.com/apache/pulsar/issues/19077#issuecomment-1366346251

   > It seems that it's due to the read position still belonging to the ledger `1174539`, so the trim ledger task will not check the ledger `1174539`, it only checks ledgers less than `1174539`.
   
   The processing that should belong to the boundary case here is inappropriate, because the calculation of entries in stats-internal starts from 1. But the position of the first message messageID in a ledger is ledgerID:entryID = 1:0. So when MarkDeletePosition is marked to 1174539:226934, it means that 226935 messages in ledger 1174539 have been Acked, because we have set retention and TTL in the background, the maximum is no more than 10 days, and this Ledger is the data of 3 months ago, so These data must be expired by TTL


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