Project

General

Profile

Bug #21225

Puppet processes consuming the whole Passenger Process Pool

Added by Eric Helms about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1472734

Description of problem:

With Satellite 6.3, the puppet is configured with PassengerMinInstances set to 16(as can be found in /etc/foreman-installer/scenarios.d/satellite-answers.yaml). Since, the default for PassengerMaxPoolSize is 12, the current setting for Puppet, doesn't allow foreman processes to run hence creating huge lag while running some operation that needs to go through foreman.

It will be better if the value for PassengerMinInstances be kept somewhere below the value of PassengerMaxPoolSize so as to allow room for foreman processes to run.

History

#1 Updated by Justin Sherrill about 3 years ago

  • Legacy Backlogs Release (now unused) set to 114

#2 Updated by Justin Sherrill about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 114 to 166
  • Status changed from New to Rejected

This is only valid for puppet 3 and we no longer support puppet 3. Closing this out.

#3 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 166 to 296
  • Assignee set to Eric Helms
  • Status changed from Rejected to Closed
  • Category deleted (Installer)
  • Project changed from Katello to Installer
  • Pull request https://github.com/theforeman/foreman-installer/pull/251 added

Also available in: Atom PDF