feat: Add connection-retry logic with exponential backoff #213
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.
Networks errors or node restarts are common scenarios in long-running operations. Under certain circumstances, the Cardano node might take a while before exposing the corresponding sockets for inbound connections. Upon initialization, if Oura isn't able to connect to the specified Cardano node, it will exit immediately with the corresponding error message.
This PR implements a configurable retry logic that will execute several connection attempts to avoid exiting prematurely if the Cardano node is still initializing. There's a delay between each attempt to avoid stressing the network stack. This delay increases exponentially up to a configurable max value.
Example configuration:
closes #201