Bootstrap check fails from insufficient vm.max_maps_count setting

[WingsLikeEagles]

Solution: Please enable the flag for disabling mmapfs (node.store.allow_mmapfs=false).

Issue: When trying to start SonarQube in a Docker container, the default setting for memory maps on most hosts is 65536 (systctl vm.max_maps_count=65536). ElasticSearch by default uses memory map file system (hybrid actually, niofs and mmapfs). It checks to see that the max map count is high enough to not run out of memory maps, and if not it tries to set the system setting "sysctl -w vm.max_map_count=262144". This fails in a Docker container as the /proc/ is mounted as Read-Only.

To get around this, Version 6.5+ of ElasticSearch allows you to disable mmapfs, and use only NIOFS. That then also removes the check for max_map_count since it's no longer using memory maps.

[WingsLikeEagles]

https://www.elastic.co/guide/en/elasticsearch/reference/7.3/index-modules-store.html#allow-mmap

[WingsLikeEagles]

elastic/elasticsearch#45815

[WingsLikeEagles]

elastic/elasticsearch#32421

[WingsLikeEagles]

Ok, so this is implemented... but the name is off...
https://jira.sonarsource.com/browse/SONAR-12264

[WingsLikeEagles]

Currently, setting this Environment Variable in the Rancher service disables using mmap and allows the container to start.
sonar.search.javaAdditionalOpts=-Dnode.store.allow_mmapfs=false

[WingsLikeEagles]

This option is available, but incorrectly named. See
https://jira.sonarsource.com/browse/SONAR-12264