-
Notifications
You must be signed in to change notification settings - Fork 896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recycled LedgerEntryImpl instances are corrupted due to invalid recycling in BK client #3104
Labels
Comments
This was referenced Mar 14, 2022
Closed
Makes sense to me. data corruption is a bad problem, "being faster" is only an enhancement. we should revert that change on master branch and on other active branches and possibly cut a new release |
This will be fixed by #3110 |
Fixed by #3110 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BUG REPORT
Describe the bug
See apache/pulsar#14436 (comment) for a detailed analysis by @congbobo184 about the symptoms of the thread safety issue.
To Reproduce
Steps to reproduce the behavior:
Follow instructions in apache/pulsar#14436
Expected behavior
BK client should handle LedgerEntryImpl instances correctly so that it would prevent the issue where entries are used in 2 threads concurrently, perhaps due to "double recycling".
The text was updated successfully, but these errors were encountered: