-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
DropPrefix: Return error on blocked writes #1329
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but Manish should probably take a look.
Reviewed 1 of 1 files at r1.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @ashish-goswami and @manishrjain)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 2 files at r2.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @ashish-goswami)
Signed-off-by: thomassong <[email protected]>
Signed-off-by: thomassong <[email protected]>
Signed-off-by: thomassong <[email protected]>
DropAll and DropPrefix both of them block writes before they start their processing. If both of them were called concurrently, one of them would panic because the other call would've blocked the writes. This PR fixes it by returning an error on blocked writes.
This change is