Multiple nodeUrls configuration #769
Closed
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
SteveYuOWO
force-pushed
the
rpc-redundancy
branch
from
74aff79
to
20d613a
Compare
|
This PR is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
|
wow, just saw this - seems exactly what I was hoping for - sucks things get set to stale and not reviewed. Can it be re-opened? |
Glad to reopen it. 😃 |
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.
Multiple nodeUrls configuration #733
nodeUrls& compatible withnodeUrlfetchJsonerrorBased on the retry mechanism, the program only needs to switch the next node when fetch error. The user had configured
nnodes. When thekthnode fetch error, failover to( k + 1 ) % nnodes.