Add response for partial object placement #33
Labels
No labels
P0
P1
P2
P3
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
2 participants
Notifications
Due date
No due date set.
Blocks
#8 Introduce
auxilliary request result
detail}
TrueCloudLab/frostfs-api
Reference: TrueCloudLab/frostfs-api#33
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Is your feature request related to a problem? Please describe.
FrostFS client sometimes can't store all required copies when some storage nodes are unavailable in container (e.g. in maintenance mode). In this case internal error is returned with
incomplete object put
message. However this does not mean that put operation was completely failed. Some nodes will store object, just less acks received than expected.Describe the solution you'd like
Introduce new error status when operation was partially successful. Add details with the number of successful acks in status details. In some cases clients will be just fine with partial success.
Describe alternatives you've considered
Keep it as it is and use copies number parameter more often.
Additional context
Related to TrueCloudLab/frostfs-node#594
maintenance
status #594The problem is that every failed PUT is "incomplete" in some sense.
I suggest reserving this status for cases when there was at least 1 or at least 1 non-local success.
auxilliary request result
detail