Actions
Bug #30789
closedPossible database connection pool exhaustion
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
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
Updated by The Foreman Bot over 4 years ago
- 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
Updated by Ewoud Kohl van Wijngaarden over 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman:puppet-foreman|026d47434316b8ae318c5e42936edc12859ab475.
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/puppet-foreman/pull/890 added
Updated by Tomer Brisker over 4 years ago
- 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
Updated by Tomer Brisker over 4 years ago
- Project changed from Foreman to Installer
Updated by Tomer Brisker over 4 years ago
- Fixed in Releases 2.2.0 added
- Fixed in Releases deleted (
2.3.0)
Updated by Ewoud Kohl van Wijngaarden over 4 years ago
- Subject changed from Possible connection pool exhaustion to Possible database connection pool exhaustion
- Triaged changed from No to Yes
Actions