Red Hat Bugzilla – Bug 989691
resource_limits.conf in prod uses different variables than in dev
Last modified: 2015-05-14 19:25:04 EDT
Description of problem:
The resource_limits.conf file in prod for small gear size specifies:
Whereas the one in dev specifies:
...and does not have a value for max_gears.
Determine which parameter is the correct one to use by inspecting the code.
If the parameters currently used in prod have no affect, determine what the effect will be once they are set properly.
Determine what's going on with max_apps. Should max_gears be set or is this a deprecated parameter.
Setting severity high until it can be determined whether prod has been running without enforcement of max_active_gears.
To be clear, we would prefer to use the resource_limits.conf files that the rpm ships.
I will remove the ones from puppet once the ones in the rpm have the values we need.
Yep, ran across this while I was resolving the differences between the two. Wasn't expecting their parameters to be different.
It looks like max_apps is no longer used. The max_active_apps parameter is silently transformed into max_active_gears inside the code.
Commit pushed to master at https://github.com/openshift/li
Bug 989691 - merge values in from production.