-
Notifications
You must be signed in to change notification settings - Fork 6.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
Stalled writes block forever during shutting down #10751
Labels
bug
Confirmed RocksDB bugs
Comments
qingping209
changed the title
CancelAllBackgroundWork does not return when there's ingestion and write stalls
Delayed writes block forever after CancelAllBackgroundWork(false) called
Sep 29, 2022
qingping209
changed the title
Delayed writes block forever after CancelAllBackgroundWork(false) called
Delayed writes block forever after CancelAllBackgroundWork called
Sep 30, 2022
Hi @qingping209 , the analysis makes sense to me, would you like to contribute a fix? |
sure. |
Closed
qingping209
changed the title
Delayed writes block forever after CancelAllBackgroundWork called
Stalled writes block forever after CancelAllBackgroundWork called
Oct 1, 2022
qingping209
changed the title
Stalled writes block forever after CancelAllBackgroundWork called
Stalled writes block forever when shutting down called
Oct 1, 2022
qingping209
changed the title
Stalled writes block forever when shutting down called
Stalled writes block forever during shutting down
Oct 1, 2022
Hey @cbi42 , Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
in the following code, the Put operation block forever.
https://gist.github.com/qingping209/356febd14f2d7db7b46212b11477ebf4
here is my reasoning:
A possible fix is to check the shutting_down_ variable in this line: https://github.com/facebook/rocksdb/blob/main/db/db_impl/db_impl_write.cc#L1787
and return Status::ok() at https://github.com/facebook/rocksdb/blob/main/db/db_impl/db_impl_write.cc#L1787
if shutting_down_ is set.
The text was updated successfully, but these errors were encountered: