You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are a few cases of node operators who experience syncing issues after upgrading to the latest CL client. Upon upgrade, syncing works, but a few hundred blocks after the CL client stops syncing. As a temporary remedy, changing the pruning setting to NOTHING works - but resetting it back to DEFAULT (to prevent state bloat) causes the original issue to come back. We should investigate what exactly is causing this to happen.
The text was updated successfully, but these errors were encountered:
Currently, there are a few cases of node operators who experience syncing issues after upgrading to the latest CL client. Upon upgrade, syncing works, but a few hundred blocks after the CL client stops syncing. As a temporary remedy, changing the
pruning
setting toNOTHING
works - but resetting it back toDEFAULT
(to prevent state bloat) causes the original issue to come back. We should investigate what exactly is causing this to happen.The text was updated successfully, but these errors were encountered: