issuing a jujud restart
Menno Smits
menno.smits at canonical.com
Mon Aug 11 02:02:42 UTC 2014
On 11 August 2014 13:48, Andrew Wilkins <andrew.wilkins at canonical.com>
wrote:
> On Mon, Aug 11, 2014 at 5:41 AM, Menno Smits <menno.smits at canonical.com>
> wrote:
>
>> How this happens is slightly complex but the short answer is that if any
>> of jujud's workers exit with a fatalError (as defined in
>> cmd/jujud/agent.go), then jujud will terminate (and then be restarted by
>> upstart).
>>
>> I'm not sure how you should propagate the need to exit from the restore
>> API call through to the worker but I'm sure that's doable.
>>
>
> We currently have ErrTerminateAgent, which signals that the agent should
> uninstall itself and then terminate. We probably just want an
> ErrRestartAgent which exits the process; upstart will restart it.
>
>
I believe this is already what will happen now if a worker returns
fatalError but creating a ErrRestartAgent and handling it appropriately
would probably be cleaner.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140811/892952b6/attachment.html>
More information about the Juju-dev
mailing list