Open siladu opened 1 year ago
@siladu do you have a status here?
@siladu do you have a status here?
@non-fungible-nelson No, it's just in the backlog. Suspect it's less of an issue on mainnet compared to Sepolia. Also suspect playing this will make this a non-issue: https://github.com/hyperledger/besu/issues/5687
@siladu when you have a moment - please revisit all these related issues and close
Split out from https://github.com/hyperledger/besu/issues/5411
Doesn't happen everytime, but easiest way to recreate is by simply restarting both clients together for an in-sync besu and nimbus pair.
Once the error is hit, it sometimes requires a restart to recover (in this case because it was cached in the bad block manager and re-requested).
besu7-restart.log nimbus-engine7-restart.log nimbus7-restart.log