lhotari opened a new issue #3104: URL: https://github.com/apache/bookkeeper/issues/3104
**BUG REPORT** ***Describe the bug*** See https://github.com/apache/pulsar/issues/14436#issuecomment-1064758710 for a detailed analysis by @congbobo184 about the symptoms of the thread safety issue. It looks like it is caused by the changes in PR #1792. The change breaks thread safety for PendingReadOp handling which doesn't have any synchronization on it's own. The design seems to rely on the fact that the request is created by the same thread that handles the response. Before PR #1792 that was the case. A network request-response call doesn't ensure happens-before and a separate solution for ensuring that would be needed unless PR#1792 is reverted. Happens-before visibility guarantee is needed since there's no synchronization in the PendingReadOp handling. ***To Reproduce*** Steps to reproduce the behavior: Follow instructions in https://github.com/apache/pulsar/issues/14436 ***Expected behavior*** BK client should not contain thread safety issues. -- 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]
