Bug #30789
closed
Possible database connection pool exhaustion
Added by Adam Ruzicka over 4 years ago.
Updated over 4 years ago.
Description
By default, we configure the db pool to have 5 available connections. However, we also configure puma to spawn 2 workers with up to 16 threads each. It is possible that if hit with enough requests, puma can run out of connections, leading to errors like:
ActiveRecord::ConnectionTimeoutError: could not obtain a connection from the pool within 5.000 seconds (waited 5.003 seconds); all pooled connections were in use
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/puppet-foreman/pull/882 added
- Status changed from Ready For Testing to Closed
- Target version set to 2.1.4
- Pull request https://github.com/theforeman/puppet-foreman/pull/890 added
- Target version changed from 2.1.4 to 2.2.0
- Fixed in Releases 2.1.4, 2.3.0 added
updating target version to make sure we don't miss this for 2.2
- Project changed from Foreman to Installer
- Category set to Foreman modules
- Fixed in Releases 2.2.0 added
- Fixed in Releases deleted (
2.3.0)
- Subject changed from Possible connection pool exhaustion to Possible database connection pool exhaustion
- Triaged changed from No to Yes
Also available in: Atom
PDF