Improve block import notification strategy #1030
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We currently use substrate block import notification stream in our pubsub module, that can lead to a race condition if a Dapp subscribes to
newHeads
and quickly after requests for data that requires the mapping in our offchain db to exist (i.e.eth_getBlockByHash
). This data may or may not exist at that moment. As in any race condition cannot be reliably reproduced but this behaviour has been reported to exist in Moonbeam several times.This PR proposes to switch to use our own Ethereum block import notification stream, that is,
send
a message through a channel when data is already mapped in our offchain db andreceive
through the channel in the pubsub subscription.