fix/small-object-parts-locking #141
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
3 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#141
Loading…
Reference in a new issue
No description provided.
Delete branch "carpawell/frostfs-node:fix/small-object-parts-locking"
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?
I decided to implement the first approach (client side pain). Could not find any more error-proof solution. May be discussed.
fix/small-object-parts-lockingto WIP: fix/small-object-parts-locking56da6f0dd8
tod491f7befe
Relations
interface fromListAllRelations
#38d491f7befe
tof9423f2e6c
f9423f2e6c
to55cb427a09
Lets merge that cause it just works. After TrueCloudLab/frostfs-sdk-go#38 is resolved, CLI code can be simplified.
WIP: fix/small-object-parts-lockingto fix/small-object-parts-locking@ -8,6 +8,7 @@ import (
"time"
objectV2 "git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/object"
internal "git.frostfs.info/TrueCloudLab/frostfs-node/cmd/frostfs-cli/internal/client"
Isn't it the same package as in the line below?
fixed
fixed
55cb427a09
toa626354b1f
@ -42,3 +47,2 @@
}
key := key.GetOrGenerate(cmd)
if _, ok := oidM[oID]; ok {
Seems like a separate feature?
well, could be considered so. i just imagined some "responsible" user that looks for all the parts of a big object and passes all of them to the
object lock
cmd. a separate commit for that?