From: Sébastien Lesaint Date: Fri, 18 Aug 2017 14:12:42 +0000 (+0200) Subject: add warning to sonar.properties about ES Virtual Memory on Linux X-Git-Tag: 6.6-RC1~470 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=3cd07e43f87d63c80519dae1f77aee84a9c49990;p=sonarqube.git add warning to sonar.properties about ES Virtual Memory on Linux --- diff --git a/sonar-application/src/main/assembly/conf/sonar.properties b/sonar-application/src/main/assembly/conf/sonar.properties index 94ba3a3a5ff..fdc340fbb6b 100644 --- a/sonar-application/src/main/assembly/conf/sonar.properties +++ b/sonar-application/src/main/assembly/conf/sonar.properties @@ -186,6 +186,17 @@ # ELASTICSEARCH # Elasticsearch is used to facilitate fast and accurate information retrieval. # It is executed in a dedicated Java process. Default heap size is 512Mb. +# +# -------------------------------------------------- +# Word of caution for Linux users on 64bits systems +# -------------------------------------------------- +# Please ensure Virtual Memory on your system is correctly configured for Elasticsearch to run properly +# (see https://www.elastic.co/guide/en/elasticsearch/reference/5.5/vm-max-map-count.html for details). +# +# When SonarQube runs standalone, a warning such as the following may appear in logs/es.log: +# "max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]" +# When SonarQube runs as a cluster, however, Elasticsearch will refuse to start. +# # JVM options of Elasticsearch process #sonar.search.javaOpts=-Xms512m \