Node/CCQ: Server auto reconnect #3611
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bruce-riley
requested review from
evan-gray,
panoel and
kev1n-peters
as code owners
evan-gray
approved these changes
Dec 21, 2023
panoel
approved these changes
Dec 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In testnet, the CCQ proxy server is not detecting when a guardian restarts. As a work around, this PR adds the ability for the server to attempt to automatically reconnect when it detects that a bootstrap peer has gone away.
This feature is only intended to be used in testnet, and is controlled by a config parameter,
monitorPeers.This PR also changes some CCQ log messages from error to debug so that routine conditions (like block not available yet) don't flood the logs.