node: Allow tombstone_lifetime config to be loaded on the fly #1405
Labels
No labels
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 project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1405
Loading…
Reference in a new issue
No description provided.
Delete branch "elebedeva/frostfs-node:feat/tombstone-reload-config"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Close #1306
Tested with
dev-env
.Signed-off-by: Ekaterina Lebedeva ekaterina.lebedeva@yadro.com
18a8aa75c8
to2d9ad9792a
2d9ad9792a
to51b9a31ee3
@ -106,2 +106,4 @@
}
ObjectCfg struct {
tombstoneLifetime uint64
We have this
uint64
and atomic in some other place.Could you describe why can't we have a single atomic?
I wanted to maintain the style of readConfig() and reloadConfig() where parameters firstly stored in
applicationConfiguration
and then are reloaded.51b9a31ee3
to57c31e9802