fix/expired-locked-object-replication #138
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
4 Participants
Notifications
Due Date
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#138
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "carpawell/frostfs-node:fix/expired-locked-object-replication"
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?
Closes #67.
@ -323,0 +338,4 @@
locked, err := v.e.IsLocked(addr)
if err != nil {
return fmt.Errorf("locking status check: %w", err)
i can imagine that we could store an object anyway in that branch but not sure. @TrueCloudLab/storage-core-committers
If there was some storage error, it would probably better not to store anything.
Also, I would somehow mention the word
expired
in the error message (can't check locking status for an expired object
?)added
@ -39,2 +40,4 @@
}
// LockSource is a source of lock relations between the objects.
type LockSource interface {
Do we really need to make this interface exportable and write comments?
we usually do such in our packages since it should be implemented in another package
in fact i would use just
StorageEngine
here but cycled imports appeared so i decided to do that as usualcc @fyrchik
We use it as an argument to the exported option, seems ok to me.
281bd7df23
to64bde68fb9