-
Notifications
You must be signed in to change notification settings - Fork 167
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
How to limit node reconnect attempts? #37
Comments
I threw together a chunk of Python code that checks the status of full node API servers prior to attempting any python-bitshares Bitshares() fullnode connections using Lomond:
Some error handling or max limit on wsconnect() attempts would still be a great redundancy step, perhaps a node could go down during script execution after having successfully checked it using the above script? |
Ran into the wsconnect retry loop after pre-checking the API node was up, need an additional/alternative solution.. |
|
I'm trying to provide redundent node connections when publishing price feeds for long periods of time.
When I try the following it gets stuck in a reconnect loop for the fist invalid server. Is there a way of providing a timeout of a max connect attempts, so that I can loop through a list of API servers?
Output:
Should I instead try to connect using a 3rd party websocket client to ping the API servers before moving ahead with creating a Bitshares instance?
Cheers
The text was updated successfully, but these errors were encountered: