on transition from gossip sync to synced download latest layers eagerly
dshulyak opened this issue · comments
2024-03-09T08:24:23.188+0100 INFO node.sync sync state change {"sessionId": "567f753f", "from state": "notSynced", "to state": "gossipSync", "current": "68824", "last synced": "68823", "latest": "68823", "processed": "68823", "name": "sync"}
2024-03-09T08:25:58.319+0100 INFO node.executor executed block {"sessionId": "aa50d170", "lid": 68824, "block": "e720cca83c", "state_hash": "789cd2098a", "duration": "27.837269ms", "count": 9, "rewards": 386, "name": "executor"}
2024-03-09T08:26:31.868+0100 INFO node.sync sync state change {"sessionId": "a472954f", "from state": "gossipSync", "to state": "synced", "current": "68825", "last synced": "68824", "latest": "68825", "processed": "68824", "name": "sync"}
in this case syncer executed 68824 , but it wasn't synced when hare for 68825 started. it won't be able to "recognize" it later, and will wait for couple of layers for hare to finish. it may result in block generator errors, due to previous layer not applied when block is ready to be built.