Ah, I was mistaken. If you set MEMORY_LIMIT, it will not get overwritten.
So if you don't set it, it will be set to the container memory limit. But
if you do set it, then the java buildpack can take advantage of it in the
way Sabha explained.
On Wed, Sep 2, 2015 at 5:18 PM, Sabha Parameswaran <sabhap(a)pivotal.io>
The MEMORY_LIMIT is used by the java buildpack to configure the various
heap parameters for a java app. This variable value is set to the container
size by default by the Cloud controller when you push the app and JBP uses
that to arrive at heap during staging.
What you have done is making the buildpack work with a lower memory
threshold even though the app itself is allowed a higher limit.
Tweak the MEMORY_LIMIT variable only when you are using JavaBP and want to
really have some additional native memory headroom to grow (due to native
memory usage or safety concerns) or to limit heap from utilizing the full
container memory size.
As Amit mentioned, always use cf scale option to change the memory or
instance count for the app container.
On Wed, Sep 2, 2015 at 4:17 PM, Siva Balan <mailsiva(a)gmail.com> wrote:
Thanks for the response. But what I am observing is, by setting
MEMORY_LIMIT as an environment variable does take effect when I restage the
app and it reduces the memory allocated to the java app(not the container
itself) to the amount set in the variable. The app is restarted with the
same heap ratio as dictated by the buildpack but assumes the max memory
available to it is now 1GB instead of 2GB. The container still had 2GB
allocated to it and I understand that will be reduced only if I use the "cf
Is this the expected behavior?
On Wed, Sep 2, 2015 at 3:55 PM, Amit Gupta <agupta(a)pivotal.io> wrote:
This is not a environment variable you can set. To scale down the
memory allocated to your instances, do
cf scale <app-name> -m 1024M
This will tell Warden/Garden to allocate that much memory to your
containers and kill them if they exceed it. The documentation is saying
that the processes running inside the container can learn about the memory
limit applied to them via the environment variable MEMORY_LIMIT. If you
try to set this variable via set-env, it will get overwritten by the value
set by "cf scale". Again, the MEMORY_LIMIT environment variable doesn't do
anything, it's just information passed into the container via the process's
environment. To actually constrain the memory, use "cf scale" or set it in
your manifest file:
On Wed, Sep 2, 2015 at 3:08 PM, Siva Balan <mailsiva(a)gmail.com> wrote:
We are not using Diego and we are on CF version 211.
I had my application started with 2GB of memory set in the manifest
file. I then ran the following command and restaged the app:
cf set-env <app-name> MEMORY_LIMIT 1024m
Then when I ran "cf app <app-name>", it was still showing the instance
memory of 2GB but the heap size allocated to the application was cut in
half and I confirmed this through New Relic app. Also, the first full GC of
the app occurred when the memory of the instance was at 1.3GB. So I am not
quite sure of the description of the MEMORY_LIMIT env variable as described
I did not see my application restart when the instance memory went over
Any ideas about this behavior?
On Tue, Sep 1, 2015 at 7:40 PM, Amit Gupta <agupta(a)pivotal.io> wrote:
On Tue, Sep 1, 2015 at 7:13 PM, Tom Sherrod <tom.sherrod(a)gmail.com>
What is the default memory size of an app deployed in diego? cf appsYes. This isn't a diego thing, this is a CC thing.
cf set-env doesn't appear to be getting the environment variableYou likely need to restage the application for ENV var changes to take
information to the running container. Is cf set-env the correct method to
effect. Unless I'm mistaken, this too is not diego-specific, and applies
to DEA containers as well.