]> source.dussan.org Git - sonarqube.git/commit
projects / sonarqube.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 191a197) | patch
SONAR-12686 MaxDirectMemorySize JVM option should be defined for ES
authorSébastien Lesaint <sebastien.lesaint@sonarsource.com>
Thu, 9 Jan 2020 08:58:26 +0000 (09:58 +0100)
committersonartech <sonartech@sonarsource.com>
Thu, 5 Nov 2020 20:06:21 +0000 (20:06 +0000)
commit3694c0d9e72a65ea7ab497b462f48850b138dcdd
tree02990c0efe2f5149250d094d56d7184e3b6b99bdtree | snapshot
parent191a19739e294985caf5c6dbce7766443533d86ccommit | diff
SONAR-12686 MaxDirectMemorySize JVM option should be defined for ES

This option was set by default in ES 6.X already but we had missed it.
ES sets it to half the max heap from Java code (see class JvmErgonomics)

To not have to get into the complexity of interpreting options to know what is the configured max heap,
we just add this option to the defaults and document it
server/sonar-process/src/main/java/org/sonar/process/ProcessProperties.java diff | blob | history
sonar-application/build.gradle diff | blob | history
sonar-application/src/main/assembly/conf/sonar.properties diff | blob | history
Continuous Inspection: https://github.com/SonarSource/sonarqube