We run several bitcoin core nodes and load balance requests across them all.

We occasionally hit the error "Block not found on disk" shortly after a new block gets confirmed, when looking up the contents of this new block. The error generally disappears when we retry after a few seconds.

Should I be worried about this error, or is it expected, since we are load-balancing requests across multiple nodes? My thinking is that possibly one of our nodes has seen the block and downloaded all of its contents, but another one of our nodes has not yet (and therefore throws the error)

  • 3
    Are you asking for a block B from node N before node N has announced it has received block B? Obviously multiple nodes in a network cannot be guaranteed to learn about the same information at the same time. – Pieter Wuille Jul 25 '20 at 0:39
  • Yes that is what I believe is happening. Likely the situation is exactly as you have described... I'm mostly asking the question to confirm that in this situation, the error "block not found on disk" would be expected, and not a cause for concern – deezy Jul 27 '20 at 0:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.