[Satellite6] How to temporarily increase passenger instances in case of foreman or candlepin performance issues?

Solution Verified - Updated -

Issue

  • foreman or candlepin having some performance issues
  • Satellite requests sometimes timeout or receive 503 response codes
  • passenger having many stuck / waiting requests

Assuming there are sufficient resources (CPU and RAM), how to tune passenger to run more concurrent Passenger RackApp processes to alleviate the problem?

Environment

Red Hat Satellite 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content