Replace blutgang with spamoor replicas #2370
Open
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.
This PR replaces the use of a load balancer (blutgang by default but ngingx also suppported) when running a single instance of spamoor with a running multiple replicas of spamoor where each target a single execution client.
This replicates how we conduct testing in our staging env we have had issues with blutgang where it was running unstably and restarting frequently. Also when scanning the blutgang logs it frequently removes nodes from the active set due to them falling behind (and then later adding them back) resulting in spamoor frequently hitting the same rpc node.
NOTE: The e2e CI test is failing, this is fixed in followup PR where we remove blutgang/nginx altogether from all integration tests