Currently, the RestartSupervisor is triggered externally by the orchestrator.
This makes some things a little complex in some cases. For instance, the restart supervisor cannot control the rate at which it is being called, leading to workarounds (#1199).
Instead, if the restart supervisor was completely independent (watching for tasks and restarting as needed) it would lead to a simpler design.
The same could perhaps apply to the UpdateSupervisor.
/cc @aaronlehmann @dongluochen
Currently, the
RestartSupervisoris triggered externally by the orchestrator.This makes some things a little complex in some cases. For instance, the restart supervisor cannot control the rate at which it is being called, leading to workarounds (#1199).
Instead, if the restart supervisor was completely independent (watching for tasks and restarting as needed) it would lead to a simpler design.
The same could perhaps apply to the
UpdateSupervisor./cc @aaronlehmann @dongluochen