On 06/21/2012 06:07 PM, R.I.Pienaar wrote:
>> 1. Puppet client runs are like bugs and a light, they will tend
>> > to cluster together. If some client runs are slow, other clients
>> > wait, over time, they all end up trying to run at the same time.
>> > This was easily observed on
On Thu, Jun 21, 2012 at 5:28 PM, Len Rugen wrote:
>
> Re: is this really still happening? I thought that got fixed ages ago
>
> I can't say, we would mask the symptoms now. Don't take the comment as a bug
> report :-)
This is actually a pretty simple patch. What would you like the
timestamp to
n Rugen"
> > To: puppet-users@googlegroups.com
> > Sent: Thursday, June 21, 2012 5:02:37 PM
> > Subject: Re: [Puppet Users] Re: Reducing system load
> >
> > Some thoughts from our similar environment:
> >
> >
> > 1. Puppet client runs are like bu
Hopefully, in the future, this feature will be added and you can determine
what is taking the longest. http://projects.puppetlabs.com/issues/2576
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https:
- Original Message -
> From: "Len Rugen"
> To: puppet-users@googlegroups.com
> Sent: Thursday, June 21, 2012 5:02:37 PM
> Subject: Re: [Puppet Users] Re: Reducing system load
>
> Some thoughts from our similar environment:
>
>
> 1. Puppet
Some thoughts from our similar environment:
1. Puppet client runs are like bugs and a light, they will tend to
cluster together. If some client runs are slow, other clients wait, over
time, they all end up trying to run at the same time. This was easily
observed on the foreman "run d
On Wednesday, June 20, 2012 1:50:38 PM UTC-5, IndyMichaelB wrote:
>
> puppet kick from your master after you make a change
>
Combining normal agent behavior with periodic kicks would increase the
workload of all parties, so I suppose you are suggesting to configure
agents to update only when k
puppet kick from your master after you make a change
--
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...@goog
On Wednesday, June 20, 2012 4:34:48 AM UTC-5, pablo.f...@cscs.ch wrote:
I really think the original question is very good: "why do you need to
> compile all manifests again and again when there is no change on the
> sources (files/ENC/whatever input)?"
>
That's a fair question, but the origi
But the way I'm reading this, the question of the OP is to reduce cpu
load on the agents, not the master. Puppet is currently unable to see
wether or not something changed on the machine since last run without
actually checking. I guess there's a bunch of indications that you
could use depending on
Hi,
I really think the original question is very good: "why do you need to
compile all manifests again and again when there is no change on the
sources (files/ENC/whatever input)?"
Tricks like the proposed ones are clearly not the solution, and even if
the language is not prepared for that t
There actually is a way to do this, though you may find it to be more
painful to work with.
Imagine, if you will, two environments: production and maintenance.
The production environment is the one you're running right now, for
production. It fully manages everything and ensures that your system
On Tuesday, June 19, 2012 5:23:42 AM UTC-5, Duncan wrote:
>
> Hi folks, I'm scratching my head with a problem with system load.
>
> When Puppet checks in every hour, runs through all our checks, then exits
> having confirmed that everything is indeed as expected, the vast majority
> of the time
13 matches
Mail list logo
