Branch: refs/heads/master
Home: https://github.com/jenkinsci/mesos-plugin
Commit: 6db07a7ffe577cce8e88d70c0d338155e59e19be
https://github.com/jenkinsci/mesos-plugin/commit/6db07a7ffe577cce8e88d70c0d338155e59e19be
Author: Vincent Latombe <vinc...@latombe.net>
Date: 2016-01-14 (Thu, 14 Jan 2016)
Changed paths:
M src/main/java/org/jenkinsci/plugins/mesos/MesosSlave.java
Log Message:
-----------
Set _JAVA_OPTIONS to use the executor memory as max heap
Recent JVMs determine automatically the max heap by taking about 1/4
of the available memory.
http://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/parallel.html#default_heap_size
The problem is that it takes as reference the host memory through
RLIMIT_AS flag value, and not the value defined by the cgroup it belongs
to.
As a consequence, if -Xmx is not explicitely specified and set to
relevant value, build processes may get killed by OOM-killer.
This takes the executor memory and set it as maximum heap size for any
forked jvm process which is what the user wants in most cases.
Commit: e1b79a4a4bb6506369fd22a6dcb81d554c11a4e9
https://github.com/jenkinsci/mesos-plugin/commit/e1b79a4a4bb6506369fd22a6dcb81d554c11a4e9
Author: Manivannan Selvaraj <maselva...@users.noreply.github.com>
Date: 2016-01-19 (Tue, 19 Jan 2016)
Changed paths:
M src/main/java/org/jenkinsci/plugins/mesos/MesosSlave.java
Log Message:
-----------
Merge pull request #191 from Vlatombe/java-options
Set _JAVA_OPTIONS to use the executor memory as max heap
Compare:
https://github.com/jenkinsci/mesos-plugin/compare/fa720b2c285b...e1b79a4a4bb6
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
