Fix node-validator's state becoming stale due to disconnected leaf stream #2051
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.
Closes #2002
This PR:
Addresses an issue that occurs when the source Leaf Stream HotShot Query service becomes unavailable, resulting in the node-validator service ending up in a Stale state with no future updates being delivered.
This is implemented with connection re-attempts to acquire a new Leaf Stream should the previous one complete. The re-attempts themselves will loop to try and ensure a new Leaf Stream is returned with an exponential backkoff up to a maximum limit of 100 times, at which point it will panic as it seems that the service is not going to be coming back immediately.