News for hackers. Stuff that matters.

A comment on Running Java in a Container.

Re:Running Java in a Container by mboehm on Wednesday March 21, 2018 @07:57AM (#16637216)
>> But the in case of containers with a hard memory limit, the entire container will simply be killed without warning.

At least in my experience that is not true. I quite often run into this issue and the OOM-killer will only kill one of the processes inside the container, not the entire container.

>> The same is true for default memory limits. The JVM looks at the host overall memory and uses that to set its defaults.

Well, I guess if you launch a JVM anywhere without setting appropriate memory settings, you are doing something fundamentally wrong.

[ Parent | on HN ]
Re:Running Java in a Container by rad_gruchalski on Wednesday March 21, 2018 @09:02AM (#16637633)
>> At least in my experience that is not true. I quite often run into this issue and the OOM-killer will only kill one of the processes inside the container, not the entire container.

Hence one does not run multiple processes in the container or / and handle crashes of potential child processes correctly.

[ Parent | on HN ]
Re:Running Java in a Container by mboehm on Wednesday March 21, 2018 @11:06AM (#16638628)
Well, I guess, sometimes you need to break the rules. But you are right.
[ Parent | on HN ]