Skip to content
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

Option to ignore uninited shards #2471

Closed
roman-khimov opened this issue Aug 4, 2023 · 0 comments · Fixed by #2953
Closed

Option to ignore uninited shards #2471

roman-khimov opened this issue Aug 4, 2023 · 0 comments · Fixed by #2953
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
Copy link
Member

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.

@roman-khimov roman-khimov added enhancement Improving existing functionality good first issue Good for newcomers neofs-storage Storage node application issues labels Aug 4, 2023
@roman-khimov roman-khimov added U2 Seriously planned S4 Routine I3 Minimal impact labels Dec 21, 2023
@roman-khimov roman-khimov added this to the v0.44.0 milestone Sep 24, 2024
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 <andrey@nspcc.io>
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 <andrey@nspcc.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants