Allow a user to turn on a modified lodestar image with more aggressive timeouts #325
Conversation
This file contains hidden or 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
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.
Some CDVN users are experiencing hangs when their cluster has two aggregators on different committees in the same slot. This causes issues as lodestar decides to skip the next slot entirely if aggregations hang past the 4 second mark.
Lodestar have released a modified image which timeouts after two seconds, which should mitigate this occurrence for the time being.
This PR allows a user to uncomment the LODESTAR_IMAGE env var, while setting LODESTAR_VERSION=obol-workaround. This will swap the standard lodestar image to this modified build, and should mitigate these skipped slots.