NLnet task 3 #667
No reviewers
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 milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#667
Loading…
Reference in a new issue
No description provided.
Delete branch "nlnet-task3"
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?
This PR tracks the progress of NLnet task 3, fixing #495 - read-after-write consistency when layout changes.
Subtask 1 (Jepsen testing): See PR #544 for details.
Subtask 2 (write and prove solution):
Subtask 3 (implementation): Mostly in this PR:
System::health()
--
FIXES:
--
LEFT FOR FUTURE PRs:
garage layout skip-dead-nodes
equivalent to admin API?garage layout skip-dead-nodes
when some nodes are unavailableSubtask 4 (re-testing): WIP, some is also in PR #544
Jepsen
WIP: NLnet task 3to WIP: NLnet task 3 subtask 3 (implementation)0f319a1c04
todf24bb806d
74109c699e
to1aab1f4e68
WIP: NLnet task 3 subtask 3 (implementation)to WIP: NLnet task 3a081e74bd7
toc539077d30
9358658cc5
to95eb13eb08
2b93daa78d
to9cecea64d4
WIP: NLnet task 3to NLnet task 3Is there any plan to effectively add this API endpoint?