Denovo1998 commented on PR #25914: URL: https://github.com/apache/pulsar/pull/25914#issuecomment-4698467699
@void-ptr974 I updated the precise time-based eviction path as suggested. The actual cursor mutation in `PersistentMessageExpiryMonitor.findEntryComplete()` now runs under the existing topic close/delete read lock. If the topic is already closing or deleting, the expiry path skips `cursor.asyncMarkDelete(...)`, resets `expirationCheckInProgress`, and returns without advancing the cursor. I also added a broker-level race test that uses a real topic/subscription/cursor: it blocks just before the expiry mark-delete, starts topic close, waits until the topic is closing/deleting, then verifies the cursor mark-delete position is not advanced. -- 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]
