On Fri, May 19, 2017 at 4:13 AM, Tim Penhey <tim.pen...@canonical.com>

> Hi folks,
> Currently juju will update the status of any hook execution for any unit
> to show that it is busy doing things. This was all well and good until we
> do things based on time.
> Every five minutes (or so) each unit will have the update-status hook
> executed to allow the unit to set or update the workload status based on
> what is currently going on with that unit.
> Since all hook executions are stored, this means that the show-status-log
> will show the unit jumping from executing update-status to ready and back
> every five minutes.
> The proposal is to special case the update-status hook and show in status
> (or the status-log) that the hook is being executed. debug-log will
> continue to show the hook executing if you are looking.
> This will reduce noise in the status-log, simplify some of our code around
> dealing with status-log, and reduce load on controllers looking after
> hundreds or thousands of units.
> Is anyone opposed to this change?
> Tim
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju-dev
Juju mailing list
Modify settings or unsubscribe at: 

Reply via email to