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/04/14 14:49:22 UTC

[GitHub] [pulsar] codelipenghui commented on pull request #15067: [ML] Follow up on race condition fixes in ManagedCursorImpl #15031

codelipenghui commented on PR #15067:
URL: https://github.com/apache/pulsar/pull/15067#issuecomment-1099265739

   @lhotari Sorry for the late response.
   
   Looks like this PR will not fix the persistentMarkDeletePosition consistency issue?
   
   Assume 2 threads, thread 0 and thread 1, thread 0 reach [here](https://github.com/apache/pulsar/pull/15067/files#diff-fad355f91bd15cc041161f9a46fce62b7fee87fbfb8f0ff8a8b724a1bd1f29eeR1883)  and thread 1 reach [here](https://github.com/apache/pulsar/pull/15067/files#diff-fad355f91bd15cc041161f9a46fce62b7fee87fbfb8f0ff8a8b724a1bd1f29eeR1852), the persistentMarkDeletePosition might apply the value from thread 0 or thread 1, it's uncertain, I think we should provide consistent behavior here.


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