Deuxfleurs/garage
41
56
Fork 73
Code Issues 99 Pull requests 14 Releases 30 Wiki Activity

Can not remove node when it is involved in an unfinished intermediate layout change #809

New issue
Open
opened 2024-04-17 18:02:45 +00:00 by yuka · 1 comment
yuka commented 2024-04-17 18:02:45 +00:00
Contributor
Copy link
$ garage layout history
==== LAYOUT HISTORY ====
Version  Status    Storage nodes  Gateway nodes
#24      current   3              0
#23      draining  4              0
#22      draining  3              0

==== UPDATE TRACKERS ====
Several layout versions are currently live in the version, and data is being migrated.
This is the internal data that Garage stores to know which nodes have what data.

Node              Ack  Sync  Sync_ack
...  #24  #22   #22
...  #24  #24   #22
...  #24  #22   #22
...  #24  #22   #22

If some nodes are not catching up to the latest layout version in the update trackers,
it might be because they are offline or unable to complete a sync successfully.
You may force progress using `garage layout skip-dead-nodes --version 24`

In version 23 I added a node, which I then removed again in version 24 without waiting for it to sync.
Now it's stuck in a state where the block sync queues are empty but the node can not be removed, not even with garage layout skip-dead-nodes --version 24 --allow-missing-data

$ garage layout skip-dead-nodes --version 23 
Error: Internal error: Nothing was done, try passing the `--allow-missing-data` flag to force progress even when not enough nodes can complete a metadata sync.

$ garage layout skip-dead-nodes --version 23 --allow-missing-data
Error: Internal error: Sorry, there is nothing I can do for you. Please wait patiently. If you ask for help, please send the output of the `garage layout history` command.

$ garage layout skip-dead-nodes --version 24
Error: Internal error: Nothing was done, try passing the `--allow-missing-data` flag to force progress even when not enough nodes can complete a metadata sync.

$ garage layout skip-dead-nodes --version 24 --allow-missing-data
Error: Internal error: Sorry, there is nothing I can do for you. Please wait patiently. If you ask for help, please send the output of the `garage layout history` command.

$
``` $ garage layout history ==== LAYOUT HISTORY ==== Version Status Storage nodes Gateway nodes #24 current 3 0 #23 draining 4 0 #22 draining 3 0 ==== UPDATE TRACKERS ==== Several layout versions are currently live in the version, and data is being migrated. This is the internal data that Garage stores to know which nodes have what data. Node Ack Sync Sync_ack ... #24 #22 #22 ... #24 #24 #22 ... #24 #22 #22 ... #24 #22 #22 If some nodes are not catching up to the latest layout version in the update trackers, it might be because they are offline or unable to complete a sync successfully. You may force progress using `garage layout skip-dead-nodes --version 24` ``` In version 23 I added a node, which I then removed again in version 24 without waiting for it to sync. Now it's stuck in a state where the block sync queues are empty but the node can not be removed, not even with `garage layout skip-dead-nodes --version 24 --allow-missing-data` ``` $ garage layout skip-dead-nodes --version 23 Error: Internal error: Nothing was done, try passing the `--allow-missing-data` flag to force progress even when not enough nodes can complete a metadata sync. $ garage layout skip-dead-nodes --version 23 --allow-missing-data Error: Internal error: Sorry, there is nothing I can do for you. Please wait patiently. If you ask for help, please send the output of the `garage layout history` command. $ garage layout skip-dead-nodes --version 24 Error: Internal error: Nothing was done, try passing the `--allow-missing-data` flag to force progress even when not enough nodes can complete a metadata sync. $ garage layout skip-dead-nodes --version 24 --allow-missing-data Error: Internal error: Sorry, there is nothing I can do for you. Please wait patiently. If you ask for help, please send the output of the `garage layout history` command. $ ```
yuka commented 2024-04-17 21:12:37 +00:00
Author
Contributor
Copy link

Indeed it seems the nodes (not even the newly added node) were still busy syncing the metadata around. So bringing the new node back online and waiting long enough fixed it. I'm currently not sure if it would also have been enough to wait, without bringing the new node back online.

Indeed it seems the nodes (not even the newly added node) were still busy syncing the metadata around. So bringing the new node back online and waiting long enough fixed it. I'm currently not sure if it would also have been enough to wait, without bringing the new node back online.
lx added the
kind
wrong-behavior
 label 2024-05-24 17:10:50 +00:00
lx added this to the v1.1 milestone 2024-05-24 17:10:53 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
update-dependencies-1.1
feat-metrics-metadata-engine
improve-secret-error-message
hotfix/1.0.0-rc1-red-ftr-wquorum
main-0.9.x
db-no-unsafe
main-0.8.x
k2v/shared_http_client
feat/website-redir
smithy2
test/compilation
poc/nomad-ci
test-ci-wait
pnet_datalink-0.33.0
optimal-layout
k2v-watch-range
db-debug-log
build-convert-db
demonstrate-cargo2nix-bug
dangerous/no-fsync
dev0.7.3
doc/benchmarks
bug/check_static
bucket-cors-more
storage-optimizations
old-main
v1.0.1
v1.0.0
v0.9.4
v1.0.0-rc1
v0.8.7
v0.9.3
v0.9.2
v0.8.6
v0.9.2-rc1
v0.9.1
v0.8.5
v0.10.0-beta1
v0.9.0
v0.9.0-rc2
v0.9.0-rc1
v0.9.0-beta4
v0.9.0-beta3
v0.9.0-beta2
v0.8.4
v0.9.0-beta1
v0.8.3
v0.8.3-rc1
format_table-v0.1.1
format_table-v0.1.0
v0.8.2
v0.8.1
v0.8.0
v0.8.0-rc2
v0.8.0-rc1
v0.8.0-dangerous-no-fsync
v0.8.0-beta2-k2v
v0.8.0-beta2
v0.8.0-beta1-k2v
v0.8.0-beta1
v0.7.99.3-k2v
v0.7.3
v0.7.3-beta2
v0.7.3-beta1
v0.7.2.1
v0.7.2
v0.7.2_ci-test-2
v0.7.2+ci-test-version
v0.7.99.2-k2v
v0.7.99.1-k2v
v0.7.99-k2v
v0.7.2-k2v
v0.7.1-admin-k2v-2
v0.7.1-admin-k2v
v0.7.1-k2v
v0.7.1
v0.7.0
v0.7.0-rc1
v0.6.1
v0.6.0
v0.6.0-rc1
v0.5.1
v0.5.0.1
v0.5.0
v0.5-beta1
v0.4.0
v0.4-rc2
v0.4-rc1
0.4-beta
0.4-alpha
v0.3.0.2
v0.3.0.1
v0.3.0
v0.2.1.5
v0.2.1
v0.2.0
0.1.1b
0.1.1
0.1.0b
0.1.0
Labels
Clear labels   
action
check-aws
The behaviour should be checked against AWS S3

  
action
discussion-needed
We need to discuss if the feature is desirable and/or better specify the envisioned behavior or technical implementation

  
action
for-external-contributors
Core team does not plan working on this in the near future however an external contribution will be reviewed & merged

  
action
for-newcomers
An issue that should be newcomer friendly.

  
action
more-info-needed
More information is needed to investigate this issue

  
action
need-funding
This issue represents lots of work, we need to find money to pay our core team work

  
action
triage-required
It's not very clear what we want to do with this issue yet, more thoughts is required

  
kind
correctness
Issues of theoretical correctness that may impact edge-case scenarios

  
kind
ideas
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims

  
kind
improvement
Feature requests that do not fall in other categories

  
kind
performance
Deceptive performance observed OR idea to improve performances

  
kind
testing
Functional tests, integration tests, Jepsen, etc.

  
kind
usability
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.

  
kind
wrong-behavior
Unintended behavior

  
prio
critical
Could impact integrity or availability of production clusters

  
prio
low
For issues that we don't want to spend time on until made absolutely necessary

  
scope
admin-api
Issues concerning the administration API

  
scope
background-healing
Background healing covers repair tasks, anti-entropy, merkle trees, etc. ; everything related to replicating data appropriately.

  
scope
build
Issues with Nix, Drone, Rust Compiler, etc.

  
scope
documentation

  
scope
k8s
Kubernetes related, including Helm Charts

  
scope
layout
Linked to the cluster layout and storage management

  
scope
metadata
Metadata Engine (LMDB, sqlite, etc.)

  
scope
ops
Operations related to operations/maintenance issue, tooling related (like CLI missing info ; impossible, too dangerous, too complicated migration, etc.)

  
scope
rpc
Linked to RPC

  
scope
s3-api
Related to the S3 API (especially compatibility issues).

  
scope
security
Cryptography-related, auth-related, authorization-related issues

  
scope
telemetry
OpenTelemetry (traces, metrics, etc.)

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
Milestone
Clear milestone
No items
No milestone
v1.1
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#809
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?