> There still a leak on Trocla database connections (latest > gem/module/hiera backend). > > I've installed a puppetserver, with only a node connected on; after 5 > days, there is 240 opened connections.
So, as you were changing a lot (new gem, module and switching to new backend) I'm not sure whether you are still the facing exactly the same issue as at the beginning, but just a different variant of it. But so let's focus on the current situation as it is the one with everything up-to-date. I dumped the situation and my current guess on what is going wrong in the module's issue tracker: https://github.com/duritong/puppet-trocla/issues/25 As you have a single node in on environment that reproduces the problem I would be happy if you could provide in the ticket more information, specifically regarding to: * How does your hiera config look like atm., so how is the trocla backend hooked into the hierarchies * How many classes does the node include during compilation * How many class parameters are triggering the trocla backend? * is the amount of connections growing over time, even if you don't change anything (no new puppet code or something like that). Estimated numbers are fine, but they should get an indication whether we have too many caches that all keep connections open, while the actual idea was to use the caches to not open too many connections. thanks and best ~pete -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cff3445a-3c2e-c115-3a14-1d5ec51e3a30%40immerda.ch. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
