Thought I'd drag this topic back to life rather than open a new one for the same issue. I'm seeing pretty much the exact same behavior on my catalog compile times. With puppet 3.1.0 and hiera-gpg 1.1.0 I'm seeing compile times usually in the 60-90-second range. This is causing a lot of agent runs to timeout or get an "end of file" error. Consolidating GPG-encrypted data into a single file doesn't seem to have any bearing on compile times.
Running the master in debug mode doesn't seem to surface any obvious issues. Has anyone made any headway on this issue? -Aaron On Wednesday, February 20, 2013 9:03:19 AM UTC-7, Jon Ward wrote: > > Hi, > > I've been using hiera for a little while and have started using the > hiera-gpg back-end for passwords etc. > > The problem is, I am seeing a massive increase in catalog compile time > when using hiera-gpg. On one particular node where there is quite a lot > going on, catalog compile time jumped from <5s to >90s. My typical compile > times have gone from around 2s to around 30s. > > I have the gpg backend listed underneath yaml in my hiera.yaml file, so > from what I understand my .gpg config files should only be interrogated if > no answer is found in the .yaml files. I only have half a dozen or so vars > stored in the .gpg files. > > By simply removing the gpg backend from hiera.yaml the compile times go > back down to normal. > > I'm using Puppet 3.1.0 installed from apt.puppetlabs.com on Debian > Squeeze & hiera-gpg 1.1.0 installed from Rubygems. > > Would appreciate any tips for debugging this problem, thanks in advance. > > Jon > -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
