-
Notifications
You must be signed in to change notification settings - Fork 38
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
Bbolt's read-only status is interpreted as a disk error #2057
Labels
Comments
carpawell
added
bug
Something isn't working
neofs-storage
Storage node application issues
2022Q4
labels
Nov 14, 2022
We could take mode mutex on read for all operations and return pre-defined |
carpawell
added a commit
that referenced
this issue
Nov 15, 2022
Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
carpawell
added a commit
that referenced
this issue
Nov 15, 2022
Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
carpawell
added a commit
that referenced
this issue
Nov 15, 2022
Includes: 1. mode change read lock operation in every exported method that r/w the underlying database; 2. returning `ErrDegradedMode` logical error if any exported method is called in degraded (without a metabase) mode. Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
carpawell
added a commit
that referenced
this issue
Nov 15, 2022
Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
I coudn't come up with an example of then this can happen (after the fix from my previous comment). |
Closed via #2059. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Some race is here. Also, I doubt moving DB to read-only mode by a node is a disk error.
The text was updated successfully, but these errors were encountered: