Option to ignore uninited shards #2471
Assignees
Labels
enhancement
Improving existing functionality
good first issue
Good for newcomers
I3
Minimal impact
neofs-storage
Storage node application issues
S4
Routine
U2
Seriously planned
Milestone
Comments
roman-khimov
added
enhancement
End-rey
added a commit
that referenced
this issue
Sep 27, 2024
Add config bool option `storage.ignore_missing_shards` which specifies whether missing shards should be ignored. If option is set to `false`, then immediately fail engine's `Open`/`Init` methods on any shard failure, otherwise continue working. Closes #2471. Signed-off-by: Andrey Butusov <[email protected]>
End-rey
added a commit
that referenced
this issue
Sep 30, 2024
Add config bool option `storage.ignore_uninited_shards` which specifies whether uninited shards should be ignored. If option is set to `false`, then immediately fail engine's `Open`/`Init` methods on any shard failure, otherwise continue working. Closes #2471. Signed-off-by: Andrey Butusov <[email protected]>
roman-khimov
added a commit
that referenced
this issue
Sep 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
#2464 changed the default behavior to more sane one, but we need an option to override it in special cases (like recovery or something).
Describe the solution you'd like
CLI/env/config option like
--ignore-missing-shards.The text was updated successfully, but these errors were encountered: