P2P: Sync mode stuck after hitting max-reversible-blocks, after restart

AntelopeIO / spring

C++ implementation of the Antelope protocol with Savanna consensus

Other

5 stars 2 forks source link

P2P: Sync mode stuck after hitting max-reversible-blocks, after restart #565

Closed heifner closed 1 month ago

heifner commented 1 month ago

After hitting max-reversible-blocks during a read-mode = irreversible sync, upon restart the node is stuck in already syncing, start sync ignored.

Hitting max-reversible-blocks should be avoided after #545. Need to investigate why node is stuck in already syncing, start sync ignored and also test #545 with the reported config.ini.

max-reversible-blocks may not work correctly with read-mode = irreversible.

heifner commented 1 month ago

This is a different issue than https://github.com/AntelopeIO/spring/issues/530. #530 got stuck when a block was rejected. This was stuck because it already had all the blocks requested in its forkdb, but none had been applied because the node was running in irrevsersible mode.