Deuxfleurs/garage
48
55
Fork 73
Code Issues 100 Pull requests 15 Releases 30 Wiki Activity

New node failing to sync after layout change #841

New issue
Closed
opened 2024-07-16 13:17:16 +00:00 by anuragbhatia · 7 comments
anuragbhatia commented 2024-07-16 13:17:16 +00:00
Copy link

Had a failure in one node. Added a new fresh node to replace it and that fresh node was added successfully in the cluster from one of other existing nodes. But when I start the data sync, I see following error in the logs on the new node:

2024-07-16T13:10:59.443373Z  WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost!
2024-07-16T13:10:59.931371Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing
2024-07-16T13:10:59.931400Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing
2024-07-16T13:10:59.931405Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing
2024-07-16T13:10:59.931408Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing
2024-07-16T13:10:59.931411Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing
2024-07-16T13:10:59.931414Z ERROR garage_rpc::layout::history: Cannot receive new layout version 8, version 7 is missing
2024-07-16T13:10:59.931416Z ERROR garage_rpc::layout::history: Cannot receive new layout version 9, version 8 is missing
2024-07-16T13:11:00.254106Z  WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost!

This node also doesn't show layout at all but does shows the the other nodes on status command.

All nodes are running dxflrs/garage:v1.0.0 docker image.

Anyone with ideas with what can be done in this case?

Had a failure in one node. Added a new fresh node to replace it and that fresh node was added successfully in the cluster from one of other existing nodes. But when I start the data sync, I see following error in the logs on the new node: ``` 2024-07-16T13:10:59.443373Z WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost! 2024-07-16T13:10:59.931371Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing 2024-07-16T13:10:59.931400Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing 2024-07-16T13:10:59.931405Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing 2024-07-16T13:10:59.931408Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing 2024-07-16T13:10:59.931411Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing 2024-07-16T13:10:59.931414Z ERROR garage_rpc::layout::history: Cannot receive new layout version 8, version 7 is missing 2024-07-16T13:10:59.931416Z ERROR garage_rpc::layout::history: Cannot receive new layout version 9, version 8 is missing 2024-07-16T13:11:00.254106Z WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost! ``` This node also doesn't show layout at all but does shows the the other nodes on status command. All nodes are running dxflrs/garage:v1.0.0 docker image. Anyone with ideas with what can be done in this case?
anuragbhatia commented 2024-07-16 13:56:11 +00:00
Author
Copy link

Just realised that very often following error is coming before the layout version error:

2024-07-16T13:54:09.921838Z ERROR garage_net::error: Error: ServerConn::run: Handshake error: performing handshake: failed opening client secret box
2024-07-16T13:54:09.922976Z ERROR garage_net::error: Error: ServerConn::run: Handshake error: performing handshake: failed opening client secret box
2024-07-16T13:54:09.923081Z ERROR garage_net::error: Error: ServerConn::run: Handshake error: performing handshake: failed opening client secret box
Just realised that very often following error is coming before the layout version error: ``` 2024-07-16T13:54:09.921838Z ERROR garage_net::error: Error: ServerConn::run: Handshake error: performing handshake: failed opening client secret box 2024-07-16T13:54:09.922976Z ERROR garage_net::error: Error: ServerConn::run: Handshake error: performing handshake: failed opening client secret box 2024-07-16T13:54:09.923081Z ERROR garage_net::error: Error: ServerConn::run: Handshake error: performing handshake: failed opening client secret box ```
maximilien added the
kind
wrong-behavior
 label 2024-07-25 19:22:39 +00:00
maximilien commented 2024-07-25 19:22:50 +00:00
Owner
Copy link

Could be related to #809

Could be related to https://git.deuxfleurs.fr/Deuxfleurs/garage/issues/809
maximilien commented 2024-07-25 19:41:45 +00:00
Owner
Copy link

This is a bug in the 1.0 release. When joining a new node to the cluster, the new node might take a while to get the layout history from other nodes. A quick solution is to copy the cluster_layout file in the data folder from an existing node into the new node, so it gets the layout history.

This is a bug in the 1.0 release. When joining a new node to the cluster, the new node might take a while to get the layout history from other nodes. A quick solution is to copy the `cluster_layout` file in the data folder from an existing node into the new node, so it gets the layout history.
quentin added
kind
usability
 and removed
kind
wrong-behavior
 labels 2024-08-07 09:37:35 +00:00
quentin added the
action
triage-required
 label 2024-08-07 09:45:45 +00:00
quentin commented 2024-08-07 09:47:01 +00:00
Owner
Copy link

I don't know if this issue is a full duplicate of #809, or some of these information must be transfered to #809 (for example because it makes #809 more critical). For now, I assign the triage-required flag to remember to get back to it later.

I don't know if this issue is a full duplicate of #809, or some of these information must be transfered to #809 (for example because it makes #809 more critical). For now, I assign the triage-required flag to remember to get back to it later.
quentin added the
scope
layout
 label 2024-08-07 10:54:33 +00:00
quentin changed title from New node failing to sync to New node failing to sync after layout change 2024-08-07 10:55:21 +00:00
aichrist commented 2024-08-10 23:46:00 +00:00
Copy link

Getting the same error when adding nodes. It is more likely when I add a node and commit layer each time I add a node:

garage 2024-08-10T23:45:17.731430Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing                                                   
garage 2024-08-10T23:45:17.731458Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing                                                   
garage 2024-08-10T23:45:17.731467Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing                                                   
garage 2024-08-10T23:45:17.731475Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing                                                   
garage 2024-08-10T23:45:17.731483Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing                                                   
garage 2024-08-10T23:45:17.914986Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing                                                   
garage 2024-08-10T23:45:17.915006Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing                                                   
garage 2024-08-10T23:45:17.915015Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing                                                   
garage 2024-08-10T23:45:17.915023Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing                                                   
garage 2024-08-10T23:45:17.915031Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing                                                   
garage 2024-08-10T23:45:19.872196Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing                                                   
garage 2024-08-10T23:45:19.872221Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing                                                   
garage 2024-08-10T23:45:19.872230Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing                                                   
garage 2024-08-10T23:45:19.872238Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing                                                   
garage 2024-08-10T23:45:19.872245Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing
Getting the same error when adding nodes. It is more likely when I add a node and commit layer each time I add a node: ``` garage 2024-08-10T23:45:17.731430Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing garage 2024-08-10T23:45:17.731458Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing garage 2024-08-10T23:45:17.731467Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing garage 2024-08-10T23:45:17.731475Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing garage 2024-08-10T23:45:17.731483Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing garage 2024-08-10T23:45:17.914986Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing garage 2024-08-10T23:45:17.915006Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing garage 2024-08-10T23:45:17.915015Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing garage 2024-08-10T23:45:17.915023Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing garage 2024-08-10T23:45:17.915031Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing garage 2024-08-10T23:45:19.872196Z ERROR garage_rpc::layout::history: Cannot receive new layout version 3, version 2 is missing garage 2024-08-10T23:45:19.872221Z ERROR garage_rpc::layout::history: Cannot receive new layout version 4, version 3 is missing garage 2024-08-10T23:45:19.872230Z ERROR garage_rpc::layout::history: Cannot receive new layout version 5, version 4 is missing garage 2024-08-10T23:45:19.872238Z ERROR garage_rpc::layout::history: Cannot receive new layout version 6, version 5 is missing garage 2024-08-10T23:45:19.872245Z ERROR garage_rpc::layout::history: Cannot receive new layout version 7, version 6 is missing ```
dominik commented 2024-08-15 15:52:57 +00:00
Copy link

I have created a potential fix for this issue here: #854

I have created a potential fix for this issue here: https://git.deuxfleurs.fr/Deuxfleurs/garage/pulls/854
👍 1
lx closed this issue 2024-08-24 11:12:40 +00:00
aichrist commented 2024-08-27 16:35:12 +00:00
Copy link

Testing latest code, not seeing the error anymore.

Testing latest code, not seeing the error anymore.
👍 1
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
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#841
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?