feat: fatal exit upon loss of connection to sequencer #24
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.
This is a hotfix that ensures the local collector exits cleanly and is brought back up by a docker compose restart policy of the snapshotter node with which it is bundled.
Checklist
Current behaviour
Currently the local collector has difficulty establishing a single TCP connection to the sequencer during times of network congestion, which causes further issues with multiplexing libp2p streams on to it.
New expected behaviour
As described in first section of issue description.
Change logs
Changed
Deployment Instructions
NA