You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/09/01 05:58:52 UTC

[GitHub] [pulsar] hrsakai commented on pull request #17343: [Broker] Fix many stacktrace log when concurrent mark delete.

hrsakai commented on PR #17343:
URL: https://github.com/apache/pulsar/pull/17343#issuecomment-1233777823

   @AnonHxy 
   I don't know we should do that.
   At least in my environment, just before calling asyncMarkDelete in ManagedCursorImpl#flush, `lastMarkDeleteEntry.newPosition` and `markDeletePosition` were same position(when the above log was output, they were  `49:106338`), so I think we can't avoid this issue even if set isDirty as true.
   https://github.com/apache/pulsar/blob/46b1239a23fd2a250b009df1e9b4a65341d299a7/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java#L3259
   


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