Project

General

Custom queries

Profile

Actions

Bug #30789

closed

Possible database connection pool exhaustion

Added by Adam Ruzicka over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
Fixed in Releases:
Found in Releases:

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
#1

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
#2

Updated by Ewoud Kohl van Wijngaarden over 4 years ago

  • Status changed from Ready For Testing to Closed
#3

Updated by Tomer Brisker over 4 years ago

  • Target version set to 2.1.4
#4

Updated by The Foreman Bot over 4 years ago

  • Pull request https://github.com/theforeman/puppet-foreman/pull/890 added
#5

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
#6

Updated by Tomer Brisker over 4 years ago

  • Project changed from Foreman to Installer
#7

Updated by Tomer Brisker over 4 years ago

  • Category set to Foreman modules
#8

Updated by Tomer Brisker over 4 years ago

  • Fixed in Releases 2.2.0 added
  • Fixed in Releases deleted (2.3.0)
#9

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

Also available in: Atom PDF