View Source Reactor.Executor (reactor v0.10.2)
The Reactor executor.
The executor handles the main loop of running a Reactor.
The algorithm is somewhat confusing, so here it is in pseudocode:
- Find any async tasks (from a previous loop) which are completed. Either recurse or continue if none are found.
- Find any async steps in the plan which are ready to run (they have no
in-edges in the graph) and start as many as possible (given the constraints
of
max_concurrencyand the state of the concurrency pool). Either start over, or continue if none are found. - Find a single synchronous step which is ready to run and execute it. If there was one then recurse, otherwise continue.
- Check if there are no more steps left in the plan (there are zero vertices). If so, collect the return value and exit, otherwise recurse.
Whenever a step is run, whether run synchronously or asynchronously, the following happens:
- When the step is successful:
a. If the step is undoable (ie
Step.can?(module, :undo)?returnstrue) then the step and the result are stored in the Reactor's undo stack. b. If the result is depended upon by another step (the graph has out-edges for the step) or the step is asking the reactor to halt then the result is stored in the Reactor's intermediate results. c. The step is removed from the graph (along with it's out-edges, freeing up it's dependents to run). - When the step is unsuccessful (returns an error tuple or raises): a. If the step can be compensated then compensation is attempted up to five times before giving up. b. The reactor iterates it's undo stack calling undo on each step.
- When a step or compensation asks for a retry then the step is placed back in the graph to be run again next iteration.
Summary
Functions
@spec run(Reactor.t(), Reactor.inputs(), Reactor.context(), Reactor.options()) :: {:ok, any()} | {:halted, Reactor.t()} | {:error, any()}
Run a reactor.
Provided a Reactor which has been planned and the correct inputs, then run the Reactor until completion, halting or failure.
You probably shouldn't call this directly, but use Reactor.run/4 instead.