fix: resubscribe subsystems when their subscription is terminated #593
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.
Fixes #577
The events broker can legitimately terminate the subscription of a subscriber, e.g. when the subscriber's event queue is full up. Various subsystems such as the scheduler would, in such a scenario, simply shutdown. Which in the case of #577 would mean no more runs could be started.
This PR changes the behaviour of the subsystems: when their subscription is terminated, they instead return an error, which triggers the subsystem to be restarted (using a backoff algorithm) rather than stop completely.