-
Notifications
You must be signed in to change notification settings - Fork 25
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
filestore - shutdown #107
Comments
I see, so far we have mostly done this to support freeing of an underlying resource so it can be reused, not necessarily to reject further operation on top of the store (assuming the process using it winds itself down correctly). Would this be feasible for you? It would be possible to add code to throw an exception after disconnect of course. |
I want to avoid corruption of konserve db. I would like to have a safe shutdown feature. Once "shutdown" is called then I am safe to terminate the app. |
Single values in konserve are written atomically and you are safe to die at any point in operation without them being in a corrupted state (unless you use |
The filestore supports async operations. I am trying to make sure my app closes down correctly
and I could not find a disconnect function of the filestore.
As such, it might happen, that when I shutdown my app that there are some threads that are still writing,
which upon terminating them forcefully might lead to a corruption in the filestore.
Any comments?
Thanks!!
The text was updated successfully, but these errors were encountered: