You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in this design document, to control intermittent errors, the recovery mechanism will have a parameter named HealthyAfter that
This pull-request implemented the restart of a pipeline to be recovered, but it was considered tackling HealthyAfter separately considering it'd increase its scope notably.
Some details
The backoff will be reset only when a pipeline processes at least one record or runs without encountering an error for a predefined time frame.
Feature description
As described in this design document, to control intermittent errors, the recovery mechanism will have a parameter named
HealthyAfter
thatThis pull-request implemented the restart of a pipeline to be recovered, but it was considered tackling
HealthyAfter
separately considering it'd increase its scope notably.Some details
backoff
will be reset only when a pipeline processes at least one record or runs without encountering an error for a predefined time frame.HealthyAfter
duration https://github.com/ConduitIO/conduit/blob/raul/restart-with-recovery/pkg/lifecycle/service.go#L55.Possible solution
Spawn a goroutine that resets the backoff after a certain time.
The text was updated successfully, but these errors were encountered: