[Epoch Sync] Error in gc: DB Not Found Error: BLOCK HEADER: 11111111111111111111111111111111 #11936
Comments
|
@robin-near should the users just ignore this warning and continue waiting for the end of sync? |
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 28, 2024
* GC prints error because the head is at genesis. Return early in that case. Otherwise while we're doing epoch sync because head remains at genesis, this keeps spamming the logs. * See #11930 for a header sync problem; a recently received block is marked as invalid because its height is too far ahead of where our head is (genesis). We fix this by not marking blocks as invalid if it's just because of height. The reason why we mark a block as invalid is because we think that the block can never be valid (e.g. due to some state disagreement) so we should not bother trying it again, but if invalid height is the issue, this is counterproductive. Closes #11930 Closes #11936
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This gets printed out once a second while the node is doing epoch sync.
The text was updated successfully, but these errors were encountered: