Bug 1202466 - OPENSHIFT_GEAR_MEMORY_MB is not updated when updating memory limits
Summary: OPENSHIFT_GEAR_MEMORY_MB is not updated when updating memory limits
Keywords:
Status: CLOSED DUPLICATE of bug 1196783
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 2.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-16 16:56 UTC by Timothy Williams
Modified: 2019-04-16 14:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-16 17:02:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Timothy Williams 2015-03-16 16:56:45 UTC
Description of problem:
When updating memory limits in /etc/openshift/resource_limits.conf, the OPENSHIFT_GEAR_MEMORY_MB environment variable on applications is not updated with the new memory limits.

Version-Release number of selected component (if applicable):
2.2

How reproducible:
Always

Steps to Reproduce:
1. Create a gear and check the value of OPENSHIFT_GEAR_MEMORY_MB
2. Increase the memory limit in /etc/openshift/resource_limits.conf, following the steps at the top of the file to instantiate the changes
3. Check the value of OPENSHIFT_GEAR_MEMORY_MB again
4. Check the actual cgroup memory limit for this application at /cgroup/memory/openshift/GEAR_UUID/memory.limit_in_bytes

Actual results:
OPENSHIFT_GEAR_MEMORY_MB does not change to reflect the new memory limit

Expected results:
OPENSHIFT_GEAR_MEMORY_MB changes to reflect the new memory limit when the memory limit is changed

Additional info:
This can have a major affect on some applications, such as ruby:

https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-ruby/versions/shared/etc/conf.d/performance.conf.erb#L5

Comment 1 Jhon Honce 2015-03-16 17:02:52 UTC

*** This bug has been marked as a duplicate of bug 1196783 ***


Note You need to log in before you can comment on or make changes to this bug.