feat: 🎸 Add process to batch block migrations #158
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.
Description
With mapping handlers, all the old blocks were tried to be processed to be mapped in newer events in a single transaction. This even though was possible was keeping the block processing thread to remain open and also used to timeout if number of processed blocks was very high (~ 6M which needed almost 3600 timeout that the
subquery-node
is currently defaulted to).This adds a max permissible block limit for migrating events data into entities to prevent timeout of block processing service. So, it fetches a set of blocks against every new block and migrates them into apt data. This will continue until all the old blocks are processed.
Breaking Changes
JIRA Link
Checklist