Issue #1491 has been updated by tstoop.
Status changed from Rejected to Re-opened
<pre>
[EMAIL PROTECTED]:~$ sudo puppetd --genconfig | grep splay
splay = true
splaylimit = 1800
[EMAIL PROTECTED]:~$ sudo puppetd --genconfig | grep -e runinterval
# runinterval = 1800
# The default value is '$runinterval'.
# The default value is '$runinterval'.
[EMAIL PROTECTED]:~$ cat /var/log/daemon.log | grep puppetd | grep catalog |
tail
Sep 16 19:27:18 test1-dom0 puppetd[2509]: Starting catalog run
Sep 16 19:27:33 test1-dom0 puppetd[2509]: Finished catalog run in 15.06 seconds
Sep 16 20:20:24 test1-dom0 puppetd[2509]: Starting catalog run
Sep 16 20:20:44 test1-dom0 puppetd[2509]: Finished catalog run in 19.80 seconds
Sep 16 21:13:38 test1-dom0 puppetd[2509]: Starting catalog run
Sep 16 21:13:53 test1-dom0 puppetd[2509]: Finished catalog run in 15.18 seconds
Sep 16 22:06:44 test1-dom0 puppetd[2509]: Starting catalog run
Sep 16 22:07:00 test1-dom0 puppetd[2509]: Finished catalog run in 15.86 seconds
Sep 16 22:59:52 test1-dom0 puppetd[2509]: Starting catalog run
Sep 16 23:00:09 test1-dom0 puppetd[2509]: Finished catalog run in 16.59 seconds
</pre>
Look at the time between runs, starting from the first:
<pre>
19:27:18 - 20:20:24 = 53 minutes 6 seconds (3186 seconds)
20:20:24 - 21:13:38 = 53 minutes 14 seconds (3194 seconds)
21:13:38 - 22:06:44 = 53 minutes 6 seconds (3186 seconds)
22:06:44 - 22:59:52 = 53 minutes 8 seconds (3188 seconds)
</pre>
>From the description of 'runinterval', I would expect that it determines at
>all times how often puppetd is run. I think splay should only added for the
>first run... So when you just start puppetd, you get the following intervals
>(example):
<pre>
12:00 start puppetd
12:13 first run (783 seconds, the random splay)
12:43 second run (1800 seconds)
13:13 third run (1800 seconds)
etc.
</pre>
As I said before, it might be some strange brainspasm of mine, if you disagree
that it should work the way I would expect, feel free to. But from reading the
documentation, this is what I would expect.
This is the text that makes me expect the behaviour I described in my example:
<pre>runinterval
How often puppetd applies the client configuration; in seconds.</pre>
Is this the explanation you wanted, Luke, or do you need more info?
----------------------------------------
Feature #1491: Splay doubles runinterval
http://projects.reductivelabs.com/issues/show/1491
Author: tstoop
Status: Re-opened
Priority: Normal
Assigned to:
Category:
Target version: 0.24.6
Complexity: Unknown
Affected version: 0.24.5
Keywords:
Not sure if this is a bug or not, so making it a feature request.
At the moment, when you use splay, the splay seems to get added every time.
This in effect doubles the runinterval. In our setup we use the default
runinterval and puppetd runs once every hour. We expected it to run every 1800
seconds, since that's what the runinterval is set for.
What we expected from splay is that it waited for a random amount of seconds
(between 0 and $runinterval) when started and after that simply use the
runinterval setting. This would seem more consistent with it's intentions. Now
it seems to change the definition of runinterval.
Let me know if I failed in explaining this correctly.
----------------------------------------
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://reductivelabs.com/redmine/my/account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
