On 04/22/2017 11:54 PM, Bill Sirinek wrote:
A side effect of this change is that my PuppetDB command queue depth
went from just over 100 to 0, and has stayed there for a couple hours
now, maybe occasionally poking up to 2-3 briefly. At least I think it
was related to this change. :)
You're probably right about that. Since you run Puppet on a regular
interval, I expect you'd have had a relatively constant number of
reports in retries at any given time, which would keep your queue
nonempty. Anyway, glad to help and that it's resolved.
Wyatt
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/18afa1b5-67c2-3235-0f99-e869d0bd201b%40puppet.com.
For more options, visit https://groups.google.com/d/optout.
