Add a local lock on CreateBucket etc, as a temporary measure #723
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#723
Loading…
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?
We have consistency issues with CreateBucket and all APIs for managing access keys and buckets (see #649).
The general solution will necessarily be to add a consensus algorithm.
In the meantime, this issue is about adding a basic lock on each node, which just prevents simultaneous operations locally. This removes the issue in the specific sub-case of API requests all going to the same API node.
lx referenced this issue2024-03-01 14:14:56 +00:00