Project

General

Profile

Actions
Copy link

Bug #21225

closed

Puppet processes consuming the whole Passenger Process Pool

Added by Eric Helms about 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Eric Helms
Category:
-
Target version:
1.17.0
Difficulty:
Triaged:
Bugzilla link:
1472734
Pull request:
https://github.com/theforeman/foreman-installer/pull/251
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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.

Actions
Copy link
 #1

Updated by Justin Sherrill about 7 years ago

  • Translation missing: en.field_release set to 114
Actions
Copy link
 #2

Updated by Justin Sherrill about 7 years ago

  • Status changed from New to Rejected
  • Translation missing: en.field_release changed from 114 to 166

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

Actions
Copy link
 #3

Updated by Eric Helms almost 7 years ago

  • Project changed from Katello to Installer
  • Category deleted (Installer)
  • Status changed from Rejected to Closed
  • Assignee set to Eric Helms
  • Translation missing: en.field_release changed from 166 to 296
  • Pull request https://github.com/theforeman/foreman-installer/pull/251 added
Actions
Copy link

Also available in: Atom PDF