Make best effort to parse placement policy on the start #168
Labels
No Label
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#168
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?
Is your feature request related to a problem? Please describe.
S3 gateway does not start if there are invalid placement policies in the config. Also all placement policies are ignored on SIGHUP reload if single policy is invalid. This makes service less robust for the errors.
Describe the solution you'd like
Ignore invalid placement policies on the startup, warn about invalid issues on logs during startup and SIGHUP reload.
Describe alternatives you've considered
Do as it done before.
Additional context
There was a load drawdown in when invalid policies appeared in the config when node restarted.