Do our best to prevent double replication while Put
handling #226
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#226
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
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?
Container policy is not restricted with any number of replicas so it is possible to have really big number of replicas. If
Put
is not parallized well (see #225), some of the first nodes can start replication beforePut
is completed => network communication duplication.Not sure if it is possible to solve at all. But we can try.
Make our best to prevent double replication while `Put` handlingto Do our best to prevent double replication while `Put` handlingClosed via #560.