Issue #3238 has been updated by Fabrice Bacchella. Priority changed from Urgent to Immediate
ActiveRecord don't manage closed connections, it just failed the query, so the solution can't be on the database server side, it must come from puppet. I changed priority to immediate. The ticket is open since 2010, and no realistic solution has been provided since. ---------------------------------------- Bug #3238: puppetmaster uses to many mysql connections https://projects.puppetlabs.com/issues/3238#change-73633 Author: Nicolas Szalay Status: In Topic Branch Pending Review Priority: Immediate Assignee: Category: stored configuration Target version: Affected Puppet version: 2.7.19 Keywords: mysql postgresql max_connections connections storeconfigs Branch: https://github.com/jamtur01/puppet/tree/tickets/2.7.x/3238 Hello, after upgrading to 0.25.4 this morning (debian package from squeeze on lenny ), I saw that the number of mysql connections increased greatly and then reached max_connections. Accordingly to the number of managed hosts and the time taken to reach the maximum connections I suppose that it uses one connection per client checkin. -- 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://projects.puppetlabs.com/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.
