fix(elasticsearch): Make bulk size the same for testnet and mainnet #8127
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.
Motivation
The bulk size for testnet is greater than mainnet which should synchronize the chain faster, however Elasticsearch has a limit of 100M per bulk. A stream of big blocks in the testnet can crash the node.
Close #7270
PR Author Checklist
Check before marking the PR as ready for review:
Solution
Make the testnet bulk size equal to the mainnet. This is 24 blocks per bulk.
Testing
I manually tested running the testnet, it syncing and adding records to the database as expected.
Review
Anyone can review.
Reviewer Checklist
Check before approving the PR:
PR blockers can be dealt with in new tickets or PRs.
And check the PR Author checklist is complete.