Feat/header injection and feat/jsonrpc_error_code_failover#6
Open
lucasjoaquimDH wants to merge 3 commits intoBlockPILabs:mainfrom
Open
Feat/header injection and feat/jsonrpc_error_code_failover#6lucasjoaquimDH wants to merge 3 commits intoBlockPILabs:mainfrom
lucasjoaquimDH wants to merge 3 commits intoBlockPILabs:mainfrom
Conversation
…, an int array that if any of the values match the jsonrpc error code, make the request failover
…to upstream RPC calls
…ilover and headers fields
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
1 participant
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 introduces two per-node configuration extensions:
Config-driven failover via jsonrpc_error_code_failover (int array): when an upstream JSON-RPC error.code (or equivalent HTTP status) matches the configured list, the request is retried against another endpoint and the current node is put into a temporary in-memory cooldown.
Per-node request headers via headers (string map): custom headers are injected into upstream requests and are cleared between retries/failovers to avoid leaking headers across providers.
It also updates the load balancer to properly skip nodes under cooldown and refreshes the README with example configurations.