ElasticSearch configuration needed as part of install process?

SonarQube Server / Community Build
1

Hi!

Environment:
SonarQube 6.7.4
Running as a service on Linux

Checking the ElasticSearch logs, es.log, I find these warnings:

WARN  es[][o.e.b.BootstrapChecks] max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
WARN  es[][o.e.b.BootstrapChecks] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

These settings seem to be easily configurable, already documented here: https://www.elastic.co/guide/en/elasticsearch/reference/current/system-config.html

I think settings these values should be documented in the Sonar install guide, somewhere around here :face_with_monocle: : https://docs.sonarqube.org/display/SONAR/Installing+the+Server What do you think?

Thanks and cheers,
Balázs

P.s.
I also have ActiveRulesPublisher issue described in: Initial setup integration failing . Still need to try the suggested fix. I have the feeling not having the warnings to begin with will help to avoid this issue in the future.

2

Hi Balázs,

Thanks for the tip. In fact, those requirements are documented here: https://docs.sonarqube.org/display/SONAR/Requirements#Requirements-Linux.

I wouldn’t want to document them in both places and have to maintain that duplication. (I suppose I could use an include, but that’s not straightforward to maintain either…).

Do you feel strongly that they really belong in one place versus the other?

Thx,
Ann

3

Hey Ann!

I missed to check the Requirements page. Honestly the docs are pretty good, the install guide even links back to the requirements page.

Since Sonar has been running successfully for a while, and the Adminstration -> System page was reporting a green state ( both overall and for the search engine state) I did not assume that I’m lacking something so important.
Without checking the logs manually it is easy to miss this.

Do you think it makes sense to improve the self reported state? “Max File Descriptors” as a metric is already available on the UI. If it warned me that I need to configure that properly, I would have caught this issue a lot earlier. With that the docs do not really need an update.

Cheers,
Balázs