fix: Cap Block Streamer Caching and Merge Redis Impl #599
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Redis memory usage is pegged at 100% due to Block Streamer backfilling * contract filter indexers.
In addition, Redis implementation of Coordinator and Block Streamer have diverged. Coordinator is also not able to make successful calls to Redis. While not a targeted fix, the hope is that merging the implementation fixes the issue as Block Streamer is able to make calls to Redis.
Before release, some manual intervention is necessary in dev and prod to update versions of indexers to the current, to prevent unwanted behavior from coordinator. I will do dev first, release the change, and then do prod before a prod release.