Wrap the given FlowFlow with a FlowFlow that will restart it when it fails or complete using an exponential backoff.

Error handling




Wrap the given FlowFlow with a FlowFlow that will restart it when it completes or fails using exponential backoff. The backoff resets back to minBackoff if there hasn’t been a restart within maxRestartsWithin (which defaults to minBackoff).

This FlowFlow will not cancel, complete or emit a failure, until the opposite end of it has been cancelled or completed. Any termination by the FlowFlow before that time will be handled by restarting it as long as maxRestarts is not reached. Any termination signals sent to this FlowFlow however will terminate the wrapped FlowFlow, if it’s running, and then the FlowFlow will be allowed to terminate without being restarted.

The restart process is inherently lossy, since there is no coordination between cancelling and the sending of messages. A termination signal from either end of the wrapped FlowFlow will cause the other end to be terminated, and any in transit messages will be lost. During backoff, this FlowFlow will backpressure.

This uses the same exponential backoff algorithm as BackoffOptsBackoffOpts.

See also:

Reactive Streams semantics

emits when the wrapped flow emits

backpressures during backoff and when the wrapped flow backpressures

completes when maxRestarts are reached within the given time limit

Found an error in this documentation? The source code for this page can be found here. Please feel free to edit and contribute a pull request.