besu Worldstate Sync Does Not Resume from where it left off following a restart

Worldstate Sync Does Not Resume from where it left off following a restart

Open non-fungible-nelson opened this issue 2 years ago • 4 comments

Description

As a user, I would like for my worldstate download to resume from where it left off if my node restarts during sync. This will give me a better UX if I have to restart my node for sync related (or unrelated) issues.

Acceptance Criteria

Worldstate sync can continue across a restart.

Steps to Reproduce (Bug)

Begin sync and restart the node
Stop node
Restart node and have world state sync start from scratch

Expected behavior: [What you expect to happen]

Begin sync and restart the node
Stop the node
Restart node and have world start sync start from where it left off

Frequency: [What percentage of the time does it occur?] All the time

Versions (Add all that apply)

Software version: 22.7.1

Aug 23 '22 15:08 non-fungible-nelson

Bump for this.

My worldstate was already completed, but my client was still syncing (importing chain segments). I restarted besu to try some java heap size options and noticed the worldstate started from 0.0%.

Aug 27 '22 21:08 terahertz5k

As a relatively new user of Besu I have restarted the service doing minor, or none, configuration changes not realising this would incur a massive downtime penalty.

Suggestion: Additional/clearer logs that communicate that the node is healthy, such that non-expert Besu users don't feel the need to turn it off and on again.