Correctly process some logical errors #211
No reviewers
Labels
No Label
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 Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#211
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "fyrchik/frostfs-node:handle-logical-errors"
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?
0ebdcdfe65
to60057f1d68
@ -62,2 +71,4 @@
return nil, ErrPiloramaDisabled
}
s.m.RLock()
lock will be held for
pilorama.TreeGetByPath
call. Is it ok?Same for other calls.
Yes, basically what we do here is to allow operations to finish before other, possibly disruptive, operations such as
SetMode
take place.Typo in commit message
the shard it not
60057f1d68
to731979a482