Deleting objects/bucket when object is missing or removed in metabase #78
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#78
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?
In #71 we fixed a case when tree service or fstree/blobovniza are missing in the storage.
However there are still cases when object is not accessible from the metabase:
We can use @dkirillov proposal:
Deleting values from tree services when
object not found
seems dangerous for me, because this error might be unrelated to actual object placement. Howeverobject is already removed
gives us some context and we can consider removing data from the tree service in this case./cc @dkirillov, @ironbee, @realloc