Cancel GC if change mode requested (SUPPORT) #384
No reviewers
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#384
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:fix/cancel_gc_on_set_mode_support"
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?
cancel GC if change mode or reload requested. Looks like GC is the most longrunning operation, so only GC affected now.
changed GC logic: now objects deleted one-by-one, metabase is the last step, because GC info is stored in metabase.
adad927544
to2753b683ad
Cancel GC if change mode requestedto Cancel GC if change mode requested (SUPPORT)cfa1b9de75
toa506da97d6