Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot sync a cardano-node using latest snapshot on GCP #344

Closed
ghost opened this issue Jul 8, 2022 · 4 comments
Closed

Cannot sync a cardano-node using latest snapshot on GCP #344

ghost opened this issue Jul 8, 2022 · 4 comments
Assignees
Labels
bug ⚠️ Something isn't working D-easy Difficulty: easy P-high Priority: high

Comments

@ghost
Copy link

ghost commented Jul 8, 2022

We (Hydra) tried to use Mithril snapshots (not (yet) verified...) from Google Storage and we encountered an issue that made the process slower than it should be: It correctly checked the immutable db but then failed at the very last stage, leading to full replay of the chain.
This seems to be related to IntersectMBO/cardano-node#4146
/cc @ch1bo for

@ghost ghost added the bug ⚠️ Something isn't working label Jul 8, 2022
@ghost
Copy link
Author

ghost commented Jul 8, 2022

Upgrading cardano-node to 1.35.1 should fix the issue

@jpraynaud
Copy link
Member

jpraynaud commented Jul 8, 2022

I have made the following test with the same snapshot archive, that was produced with Cardano node 1.35.0:

  • Restore with 1.35.0 Cardano node: the ledger state embedded in the snapshot is ignored, and the node re-computes it from the beginning (which is very long)
  • Restore with 1.35.1 Cardano node: the ledger state embedded in the snapshot is used and the startup time as fast as it used to be with 1.34.1 Cardano node

Upgrading to 1.35.1 is definitely the solution 👍

@jpraynaud jpraynaud self-assigned this Jul 8, 2022
@ghost
Copy link
Author

ghost commented Jul 8, 2022

Thanks for checking @jpraynaud , not sure if there's any action to take here, feel free to close the issue :)

@jpraynaud
Copy link
Member

OK, I close the issue as there is nothing more that we can do on our end 👍

@jpraynaud jpraynaud added P-high Priority: high D-easy Difficulty: easy labels Jul 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ⚠️ Something isn't working D-easy Difficulty: easy P-high Priority: high
Projects
None yet
Development

No branches or pull requests

1 participant