Need to make process of verify node config more intelligent #111
Labels
No Label
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#111
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Original issue: https://github.com/nspcc-dev/neofs-node/issues/1950
I have case with mistake in config, which lead to part of config was not used.
Config with mistake:
In this case
default:
section was in theshard.0
section. But it should be at the same level. This mistake have lead to ``default``` section was ignored by node.We should make the process of verify node config more intelligent.
Related TrueCloudLab/frostfs-http-gw#14