Comment 13 for bug 1006553

restarting zookeeper will stop the cpu load as the machine agent will be
able to connect. However the containers would still need to be started, the
machine agent should do this, but i don't believe its implemented as such
yet (detecting existing container and restarting vs starting new).


On Tue, Jun 26, 2012 at 8:56 AM, Neal McBurnett <email address hidden>wrote:

> Adrien, I agree, something less destructive than juju destroy-
> environment would be helpful for people that run into this. The "lxc-
> list" command will show which containers exist, but juju destroy-service
> fails for me after a reboot also. It's still unclear how to avoid cpu
> churning but also preserve the environment.
> Is there a workaround to cleanly resume after reboot, restarting the
> zookeeper, agents, etc?
> --
> You received this bug notification because you are subscribed to juju.
> Title:
> Juju uses 100% CPU after host reboot
> To manage notifications about this bug go to: