near-api-js
near-api-js copied to clipboard
near
Failover configuration
Closing #733
- Added support for multiple API Keys (since we can have multiple RPC Servers)
- Added basic failover functionality
With this design of failover, we will change (rotate) our server when needed and stick to this new server for our next calls. It will help to avoid long responses when first (or more) servers are down.
For now, server rotation is happening only on Timeout error.
Also, check this comment: https://github.com/near/near-api-js/issues/733#issuecomment-998869162
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.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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.
Is this PR ready? This allows failover logic with config for multiple RPC providers?
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.
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.
@MaximusHaximus @vgrichina @volovyk-s Any updates here? This change is very needed for all dapps!
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.
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.
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.
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.
@MaximusHaximus this PR still needs review. People are demanding such functionality. If general architecture will be approved, we can continue polishing it.
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.
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.
This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or this will be closed in another 7 days.
This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or this will be closed in another 7 days.
This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or this will be closed in another 7 days.
Hey @frol, do you want this PR to be merged? If so, we suggest closing the existing PR and moving all the changes to a new one. It will be much easier for us to resolve the conflicts that way. What do you think?
It will be much easier for us to resolve the conflicts that way. What do you think?
Sure, makes sense. I would keep this PR open until a new one is submitted, so we don't lose track of it.
