[#279] pool: Count maintenance mode errors in object search #288
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
pool
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-sdk-go#288
Loading…
Reference in a new issue
No description provided.
Delete branch "mbiryukova/frostfs-sdk-go:bugfix/count_mm_errors"
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?
Closes #279
Signed-off-by: Marina Biryukova m.biryukova@yadro.com
@ -2721,2 +2722,4 @@
}
switch err.(type) {
case *apistatus.NodeUnderMaintenance:
I would expect that we will use
handleError
here to handle all errors, not only maintenanceIt looks very tricky, especially given that we return the error after that.
Can we handle it where
Read
is called?But if I understand correctly,
Read
can be called outside pool, in which case we can't count this error8da1a69d2b
to5594551a52
LGTM
Is it possible to add some tests?