port: tree: Support removing old split system nodes #444
No reviewers
Labels
No labels
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 project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#444
Loading…
Reference in a new issue
No description provided.
Delete branch "alexvanin/frostfs-s3-gw:port/settings-split"
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?
It's need to fit user expectation on deleting CORS for example. Previously after removing cors (that was uploaded in split manner) we can still get some data (from other node) because deletion worked only for latest node version.
Port of #437 into master
@ -118,2 +113,2 @@
if err = n.objectDeleteWithAuth(ctx, corsBkt, obj.Object(), prmAuth); err != nil {
return fmt.Errorf("delete cors object: %w", err)
for _, addr := range objs {
n.deleteCORSObject(ctx, bktInfo, addr)
@mbiryukova is this change legal? We've used
deleteCORSObject
inPutBucketCORS
so I've decided to reuse it inDeleteBucketCORS
. Can I do that?The only difference is that error was returned. With multiple deletions I guess it's ok to just log them
c81f3df9e3
to5baa6c045d
5baa6c045d
to41eda7aa35
@ -510,3 +566,4 @@
return objToDelete, nil
}
func getCORSAddress(node *treeNode) (oid.Address, error) {
Let's rename this function to
getTreeNodeAddress
for example