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

Failed to prune, v1.1.0 and v1.2.1 err="no snapshot paired state" #1117

Closed
kompotkot opened this issue Dec 28, 2023 · 7 comments
Closed

Failed to prune, v1.1.0 and v1.2.1 err="no snapshot paired state" #1117

kompotkot opened this issue Dec 28, 2023 · 7 comments

Comments

@kompotkot
Copy link

kompotkot commented Dec 28, 2023

System information

Bor client version:

Version: 1.1.0
GitCommit: cf18eccee65ab339facbdc5a69a91be0fadd9d39
Version: 1.2.1
GitCommit: 2ee39192bd5c60f9fd6baa946ae774c6d629e714

Heimdall client version:

1.0.3
INFO [2023-12-28|10:11:48.819] Heimdall services stopped                    module=cmd/heimdalld

OS & Version: Linux Ubuntu 20.04

Environment: Polygon Mainnet

Type of node: Sentry

Overview of the problem

Raised exception by bor client during prune workflow. Tried with v1.2.0, upgrade to v1.2.1 and downgrade to v1.1.0 not helped. Before prune after upgrades and downgrades node synced for a while (~12 hours).

Reproduction Steps

  1. Start prune with command:
sudo -u bor /usr/bin/bor snapshot prune-state --datadir /mnt/disks/polygon/bor/data

Logs / Traces / Output / Error Messages

Prune:

v1.1.0_prune

v1.2.1_prune

Node shutdown:

bor_shutdown

Node start:

node_start_1

node_start_2

@kompotkot kompotkot changed the title Failed to prune, v1.1.0 and v1.2.2 err="no snapshot paired state" Failed to prune, v1.1.0 and v1.2.1 err="no snapshot paired state" Dec 28, 2023
@kompotkot
Copy link
Author

Described solutions in Issue #1104 not helped.

@temaniarpit27
Copy link
Contributor

We will be releasing out a fix soon. Thanks for your patience

@icculp
Copy link

icculp commented Jan 4, 2024

Same on 1.2.1 with fresh snapshot download.

@kompotkot
Copy link
Author

I tried with

Version: 1.2.2
GitCommit: 70bebc933555439afa6b24b61b39c1303bbf2f1f

Same result :(

@temaniarpit27
Copy link
Contributor

Can you please let your node sync to the tip with v1.2.2 and then stop the bor node and then try pruning? @kompotkot

@kompotkot
Copy link
Author

Can you please let your node sync to the tip with v1.2.2 and then stop the bor node and then try pruning? @kompotkot

It started working!

INFO [01-15|15:06:48.449] Initialized state bloom                  size=2.00GiB
INFO [01-15|15:07:03.985] Selecting bottom-most difflayer as the pruning target root=44cc7a..f10ded height=52,355,828
INFO [01-15|15:07:03.990] Iterating state snapshot                 accounts=0 slots=0 elapsed=1.114ms
INFO [01-15|15:07:11.991] Iterating state snapshot                 accounts=127,754 slots=609,292 elapsed=8.002s  eta=5h4m54.551s
INFO [01-15|15:07:19.991] Iterating state snapshot                 accounts=326,654 slots=1,257,110 elapsed=16.002s eta=3h59m20.504s
...

I can confirm, it solved my issue with next steps:

  • Updated node with maticnetwork/install/main/bor.sh script to v1.2.2 with GitCommit 70bebc933555439afa6b24b61b39c1303bbf2f1f.
  • Synchronized node for 1-2 hours.
  • Gracefully shutdown bor and heimdalld, no errors notices, confirmed Writing snapshot state to disk in log.
  • Started prune workflow as before.

Thank you!

@temaniarpit27
Copy link
Contributor

Closing this issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants