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
We should be able to remotely shut down a manager from the server. As we cannot do this actively (sending a signal directly to the manager) we need to do it passively. A suggest pathway is in the meta field of a all Manager REST calls we should check for a field called remote_shutdown or similar. If this is ever True the manager should shutdown and exit. This has two parts:
Placing hooks in the manager to allow shutdown. @Lnaden
Having the server emit this shutdown message. @dgasmith
In addition we should consider a field like shutdown_reason that would be presented in the logs.
The text was updated successfully, but these errors were encountered:
On Mon, Sep 30, 2019 at 6:14 AM Daniel Smith ***@***.***> wrote:
We should be able to remotely shut down a manager from the server. As we
cannot do this actively (sending a signal directly to the manager) we need
to do it passively. A suggest pathway is in the meta field of a all
Manager REST calls we should check for a field called remote_shutdown or
similar. If this is ever True the manager should shutdown and exit. This
has two parts:
- Placing hooks in the manager to allow shutdown. @Lnaden
<https://github.com/Lnaden>
- Having the server emit this shutdown message. @dgasmith
<https://github.com/dgasmith>
In addition we should consider a field like shutdown_reason that would be
presented in the logs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#416?email_source=notifications&email_token=AD4STV5MFLGQZFCE6HFBQTDQMH3UVA5CNFSM4I32YBMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HORQJ7Q>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD4STVZXZ4JH5UK2GCVDZJ3QMH3UVANCNFSM4I32YBMA>
.
We should be able to remotely shut down a manager from the server. As we cannot do this actively (sending a signal directly to the manager) we need to do it passively. A suggest pathway is in the
meta
field of a all Manager REST calls we should check for a field calledremote_shutdown
or similar. If this is ever True the manager should shutdown and exit. This has two parts:In addition we should consider a field like
shutdown_reason
that would be presented in the logs.The text was updated successfully, but these errors were encountered: