Hide Forgot
Currently, memory.move_charge_at_immigrate is set to 0 in the cgroup configuration of OpenShift Online nodes. This means that when a process is moved into a gear's cgroup after its initial execution, the memory usage up to that point is not charged to the cgroup. See Section 8 of https://www.kernel.org/doc/Documentation/cgroups/memory.txt
Pull request: https://github.com/openshift/origin-server/pull/3555
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/67439510c97799c8d88e080009f49fcc4a7b27bd Bug 1004886 - set memory.move_charge_at_immigrate
Commit pushed to master at https://github.com/openshift/li https://github.com/openshift/li/commit/f7db910abca4bc3ff9f240fdad0a068e893eb233 Bug 1004886 - set memory.move_charge_at_immigrate
[jbeap1-bmengdev.dev.rhcloud.com 52299a830b193ec283000003]\> oo-cgroup-read memory.move_charge_at_immigrate 1 Checked on devenv_3751, issue has been fixed.