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

Migration 0.9.0 -> 1.0.1: Unable to decode persisted data file #884

New issue
Closed
opened 2024-09-25 18:49:33 +00:00 by vk · 3 comments
vk commented 2024-09-25 18:49:33 +00:00
Copy link

Hello,

I'm preparing the migration of my cluster from 0.9.0 to the latest 1.0.1.

As a rehearsal, I have cloned one of the nodes' meta folder (after clean shutdown), and moved it to a test VM with 1.0.1 installed.

I'm getting the following error entry in log, during the first (only) updated node startup:

ERROR garage_util::persister: Unable to decode persisted data file /garage/meta/data_layout

Should I be worried?

Here's the full log of the first node startup:

2024-09-25T18:37:02.798423Z  INFO garage::server: Loading configuration...
2024-09-25T18:37:02.798601Z  INFO garage::server: Initializing Garage main data store...
2024-09-25T18:37:02.798633Z  INFO garage_model::garage: Opening database...
2024-09-25T18:37:02.798641Z  INFO garage_db::open: Opening LMDB database at: /garage/meta/db.lmdb
2024-09-25T18:37:02.799118Z  INFO garage_model::garage: Initializing RPC...
2024-09-25T18:37:02.799129Z  WARN garage_rpc::replication_mode: Legacy config option replication_mode in use. Please migrate to replication_factor and consistency_mode
2024-09-25T18:37:02.799132Z  INFO garage_model::garage: Initialize background variable system...
2024-09-25T18:37:02.799134Z  INFO garage_model::garage: Initialize membership management system...
2024-09-25T18:37:02.799171Z  INFO garage_rpc::system: Node ID of this node: 77f0e939aaa1bf6e
2024-09-25T18:37:02.858039Z  INFO garage_model::garage: Initialize block manager...
2024-09-25T18:37:02.858125Z ERROR garage_util::persister: Unable to decode persisted data file /garage/meta/data_layout
2024-09-25T18:37:02.858703Z  INFO garage_model::garage: Initialize bucket_table...
2024-09-25T18:37:02.858782Z  INFO garage_model::garage: Initialize bucket_alias_table...
2024-09-25T18:37:02.858842Z  INFO garage_model::garage: Initialize key_table_table...
2024-09-25T18:37:02.858925Z  INFO garage_model::garage: Initialize block_ref_table...
2024-09-25T18:37:02.858988Z  INFO garage_model::garage: Initialize version_table...
2024-09-25T18:37:02.859048Z  INFO garage_model::garage: Initialize multipart upload counter table...
2024-09-25T18:37:02.859165Z  INFO garage_model::garage: Initialize multipart upload table...
2024-09-25T18:37:02.859231Z  INFO garage_model::garage: Initialize object counter table...
2024-09-25T18:37:02.859300Z  INFO garage_model::garage: Initialize object_table...
2024-09-25T18:37:02.859355Z  INFO garage_model::garage: Load lifecycle worker state...
2024-09-25T18:37:02.859406Z  INFO garage_model::garage: Initialize K2V counter table...
2024-09-25T18:37:02.859482Z  INFO garage_model::garage: Initialize K2V subscription manager...
2024-09-25T18:37:02.859487Z  INFO garage_model::garage: Initialize K2V item table...
2024-09-25T18:37:02.859550Z  INFO garage_model::garage: Initialize K2V RPC handler...
2024-09-25T18:37:02.859566Z  INFO garage::server: Initializing background runner...
2024-09-25T18:37:02.859575Z  INFO garage::server: Spawning Garage workers...
2024-09-25T18:37:02.859601Z  INFO garage::server: Initialize Admin API server and metrics collector...
2024-09-25T18:37:02.923904Z  INFO garage::server: Launching internal Garage cluster communications...
2024-09-25T18:37:02.923927Z  INFO garage::server: Create admin RPC handler...
2024-09-25T18:37:02.923941Z  INFO garage::server: Initializing S3 API server...
2024-09-25T18:37:02.923948Z  INFO garage::server: Initializing web server...
...

Thanks!

Hello, I'm preparing the migration of my cluster from 0.9.0 to the latest 1.0.1. As a rehearsal, I have cloned one of the nodes' meta folder (after clean shutdown), and moved it to a test VM with 1.0.1 installed. I'm getting the following error entry in log, during the first (only) updated node startup: ` ERROR garage_util::persister: Unable to decode persisted data file /garage/meta/data_layout ` Should I be worried? Here's the full log of the first node startup: ``` 2024-09-25T18:37:02.798423Z INFO garage::server: Loading configuration... 2024-09-25T18:37:02.798601Z INFO garage::server: Initializing Garage main data store... 2024-09-25T18:37:02.798633Z INFO garage_model::garage: Opening database... 2024-09-25T18:37:02.798641Z INFO garage_db::open: Opening LMDB database at: /garage/meta/db.lmdb 2024-09-25T18:37:02.799118Z INFO garage_model::garage: Initializing RPC... 2024-09-25T18:37:02.799129Z WARN garage_rpc::replication_mode: Legacy config option replication_mode in use. Please migrate to replication_factor and consistency_mode 2024-09-25T18:37:02.799132Z INFO garage_model::garage: Initialize background variable system... 2024-09-25T18:37:02.799134Z INFO garage_model::garage: Initialize membership management system... 2024-09-25T18:37:02.799171Z INFO garage_rpc::system: Node ID of this node: 77f0e939aaa1bf6e 2024-09-25T18:37:02.858039Z INFO garage_model::garage: Initialize block manager... 2024-09-25T18:37:02.858125Z ERROR garage_util::persister: Unable to decode persisted data file /garage/meta/data_layout 2024-09-25T18:37:02.858703Z INFO garage_model::garage: Initialize bucket_table... 2024-09-25T18:37:02.858782Z INFO garage_model::garage: Initialize bucket_alias_table... 2024-09-25T18:37:02.858842Z INFO garage_model::garage: Initialize key_table_table... 2024-09-25T18:37:02.858925Z INFO garage_model::garage: Initialize block_ref_table... 2024-09-25T18:37:02.858988Z INFO garage_model::garage: Initialize version_table... 2024-09-25T18:37:02.859048Z INFO garage_model::garage: Initialize multipart upload counter table... 2024-09-25T18:37:02.859165Z INFO garage_model::garage: Initialize multipart upload table... 2024-09-25T18:37:02.859231Z INFO garage_model::garage: Initialize object counter table... 2024-09-25T18:37:02.859300Z INFO garage_model::garage: Initialize object_table... 2024-09-25T18:37:02.859355Z INFO garage_model::garage: Load lifecycle worker state... 2024-09-25T18:37:02.859406Z INFO garage_model::garage: Initialize K2V counter table... 2024-09-25T18:37:02.859482Z INFO garage_model::garage: Initialize K2V subscription manager... 2024-09-25T18:37:02.859487Z INFO garage_model::garage: Initialize K2V item table... 2024-09-25T18:37:02.859550Z INFO garage_model::garage: Initialize K2V RPC handler... 2024-09-25T18:37:02.859566Z INFO garage::server: Initializing background runner... 2024-09-25T18:37:02.859575Z INFO garage::server: Spawning Garage workers... 2024-09-25T18:37:02.859601Z INFO garage::server: Initialize Admin API server and metrics collector... 2024-09-25T18:37:02.923904Z INFO garage::server: Launching internal Garage cluster communications... 2024-09-25T18:37:02.923927Z INFO garage::server: Create admin RPC handler... 2024-09-25T18:37:02.923941Z INFO garage::server: Initializing S3 API server... 2024-09-25T18:37:02.923948Z INFO garage::server: Initializing web server... ... ``` Thanks!
maximilien commented 2024-11-02 23:06:26 +00:00
Owner
Copy link

If I remembrer correctly this could be to the node ID being different

If I remembrer correctly this could be to the node ID being different
vk commented 2024-11-05 17:16:30 +00:00
Author
Copy link

The node id was preserved as per garage node id (it's a filesystem-level clone of one of the production nodes, so everything is there, both data and the meta, only the network is off). I suspect I may safely ignore this message, yet I'd really like to be totally sure before proceeding.

Thanks

The node id was preserved as per `garage node id` (it's a filesystem-level clone of one of the production nodes, so everything is there, both data and the meta, only the network is off). I suspect I may safely ignore this message, yet I'd really like to be totally sure before proceeding. Thanks
lx commented 2024-11-07 11:07:18 +00:00
Owner
Copy link

Yes it's fine to ignore, sorry for the late answer

Yes it's fine to ignore, sorry for the late answer
lx closed this issue 2024-11-07 11:07:18 +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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 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#884
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?