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

Add historic_roots and historic_state directories to snapshot for the archival node #1474

Closed
DmytroNazarenko opened this issue Mar 23, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request epic:archive-node epic:snapshots Snapshot functionality bugs and enhancements

Comments

@DmytroNazarenko
Copy link
Collaborator

To start the archival node from the snapshot from a custom peer, need to add to the snapshot 2 directories historic_roots and historic_state
Need to be sure, that the archival node does support the historical state before downloading the snapshot.

Related to #1144

@DmytroNazarenko DmytroNazarenko added enhancement New feature or request proposal Proposal for next release labels Mar 23, 2023
@DmytroNazarenko DmytroNazarenko added epic:archive-node epic:snapshots Snapshot functionality bugs and enhancements and removed proposal Proposal for next release labels Mar 31, 2023
@oleksandrSydorenkoJ
Copy link

Consensus databases on the archival node are rotated as on core nodes and after 4th rotation skaled invoke blocks prune for the 1st database.
To avoid losing data and the ability to start the archival node, need to add historic_roots and historic_state directories to the snapshot

@github-project-automation github-project-automation bot moved this to Ready For Release Candidate in SKALE Engineering 🚀 Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request epic:archive-node epic:snapshots Snapshot functionality bugs and enhancements
Projects
Archived in project
Development

No branches or pull requests

3 participants