"Phil Endecott" <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> On Thu, Aug 23, 2007 at 11:13:49PM +0100, phil wrote: >>> It seems that by default the munin-node program waits for 10 >>> seconds for a plugin to respond. This value is present in the >>> source of munin-node and can be over-ridden by a setting in >>> munin-node.conf. I suggest that the default munin-node.conf >>> should set a higher value. >> >> Increasing the default will create other problems. > > Could you elaborate on that a bit please?
When you increase the number of munin nodes, as well as increasing the number of plugins on each node, you will at the same time increase the risk of munin-update not being able to finish in 5 minutes. The other scripts, munin-limits, munin-graph, and munin-html can wait if needed, but for munin to have correct data, munin-update must be able to finish. Therefore I am very reluctant to increase the _default_ wait time for a plugin to respond, that should be a site local decision. The defaults should be safe and conservative. Another tip: When scaling munin, you good results if you spend a bit of time to put longer-running plugins in cron, and getting munin-node to quickly get the results from file. The less time and resources munin spends waiting for its nodes, the better. The "apt" plugin is a good example of this. -- Stig Sandbeck Mathisen, Linpro -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
