On Thu, Nov 3, 2011 at 8:36 AM, Jo Rhett <jrh...@netconsonance.com> wrote:

> For a long time it appeared that run cycles were fairly balanced -- a few
> every 30 seconds over the 30 minute period.  Right now I'm seeing more than
> 100 systems hit in the same minute: 28 and 58 minutes after the hour.  Is
> there some way to alter the spread of these systems back to even out the
> load?
>
> Or passenger options which could limit the effects of this?
>

In your puppet.conf agent block:

    # How often puppet agent applies the client configuration; in seconds.
    # Note that a runinterval of 0 means "run continuously" rather than
    # "never run." If you want puppet agent to never run, you should start
    # it with the `--no-client` option.
    # The default value is '1800'.
    runinterval = 1800

...

    # The maximum time to delay before runs.  Defaults to being the same as
the
    # run interval.
    # The default value is '$runinterval'.
    splaylimit = 1800

...

    # Whether to sleep for a pseudo-random (but consistent) amount of time
before
    # a run.
    splay = false






>
> --
> Jo Rhett
> Net Consonance : consonant endings by net philanthropy, open source and
> other randomness
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Nigel Kersten
Product Manager, Puppet Labs

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to