Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Change By: Kenneth Barber Sprint: PuppetDB2014-12- 03 17 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Change By: Ryan Senior Sprint: PuppetDB2014- 11 12 - 19 03 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Ryan Senior commented on an issue Re: Observed PuppetDB database connection leak We're using a connection pool to manage our database connections. The pool can leave connections open and then lazily reclaim them, that wouldn't surprise me. You could be seeing that? From what you observed though, it looks like conn-lifetime might not be working? That seems like it's a bug we should look into. Add Comment PuppetDB / PDB-953 Observed PuppetDB database connection leak (This was reported by a customer) Yesterday I cutover from an old to a new PuppetDB infrastructure based on PuppetDB 1.6.3.1 in PE 3.3.1 (pe-puppetdb-1.6.3.1-1.el6.noarch). Not long after we cutover I experienced an issue which hadn't previously appeared in the old environment. The number of connections to the PostgreSQL backend (pe-postgresql-9.2.7-9.pe... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Change By: Ryan Senior Sprint: PuppetDB2014-11- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Issue Type: Bug Affects Versions: 1.6.3 Assignee: Unassigned Created: 13/Oct/14 7:43 AM Labels: support Priority: Normal Reporter: Lee Lowder (This was reported by a customer) Yesterday I cutover from an old to a new PuppetDB infrastructure based on PuppetDB 1.6.3.1 in PE 3.3.1 (pe-puppetdb-1.6.3.1-1.el6.noarch). Not long after we cutover I experienced an issue which hadn't previously appeared in the old environment. The number of connections to the PostgreSQL backend (pe-postgresql-9.2.7-9.pe.el6.x86_64) continued to climb until we hit the maximum number of allowed connections in Postgres and PuppetDB (and the Console) were no longer able to make new connections and the environment ground to a halt. I did not see this behavior in any of my pre-cutover testing in the new environment so it may be only something occurs under sustained load, though it is possible it may have been there but gone unobserved. I have run a number of tests and I believe I have isolated the configuration setting responsible for the behavior. My tests point to conn-lifetime in PuppetDB's database.ini file as the culprit. The scenario I originally started with is that I had PuppetDB's database.ini file set with the following:
Jira (PDB-953) Observed PuppetDB database connection leak
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-953 Observed PuppetDB database connection leak Change By: Kenneth Barber Sprint: PuppetDB2014-11-05 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
