Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch RPC on receiving error, or random selection of RPCs each tx/query #196

Open
MathNodes opened this issue May 26, 2024 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@MathNodes
Copy link

Is your feature request related to a problem? Please describe.
When adding multiple RPCs into the config.toml, it doesn't do anything noticeable when the server receives an error such as

2024-05-20T18:02:50Z ERR failed to prepare the transaction error="post failed: Post \"https://rpc.noncompliant.network:443\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"
2024-05-20T18:02:50Z INF Preparing the transaction messages=1
2024-05-20T18:02:50Z INF Querying the account address=sent1cnp8cwxtkvuecjss7vcv32aa3kq9lkhmmgerem
2024-05-20T18:03:20Z ERR failed to prepare the transaction error="post failed: Post \"https://rpc.noncompliant.network:443\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"

Describe the solution you'd like
Upon receiving an RPC error, the dvpn-node software should rotate to the next RPC in the comma delineated list. This will help keep nodes online when one or more RPCs are failing.

Or, select RPCs at random from the comma delineated list in config.toml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants