SonarQube, ElasticSearch and Docker.

1,061 views
Skip to first unread message

Bartlomiej Palmowski

unread,
Oct 27, 2015, 1:48:59 PM10/27/15
to SonarQube
Hi,

I'm planning to dockerize my sonar installation (so it will be easier to move around and test new sonar versions, mostly as a convenience for myself, it is not supposed to be universal docker container). The only problem that I can find with dockerizing sonarqube is that it uses embedded elasticsearch (which keeps data locally in the installation dir). The question is, how the elasticsearch is currently used and how it is going to be used in the future? Can I safely assume that the es is used only as a local cache for the sql database (so every time I restart sonarqube I can remove the local data safely and it will be restored, the only cost being longer startup time)? If not, then can I use external elasticsearch instance?

Simon Brandhof

unread,
Oct 27, 2015, 4:33:15 PM10/27/15
to Bartlomiej Palmowski, SonarQube
Hi,

Elasticsearch is indeed a volatile index of database. It's automatically restored when the data directory is removed, but it can be long, very long. All depends on the number of issues and until v5.1 on the number of lines of code.
Note that the data directory can be moved outside the installation directory thanks to the property sonar.path.data.

can I use external elasticsearch instance?

No, only the embedded instance can be used.

Regards 


Simon BRANDHOF | SonarSource
Tech Lead & Co-Founder
http://twitter.com/SimonBrandhof

On 27 October 2015 at 18:48, Bartlomiej Palmowski <wszystkie.fajn...@gmail.com> wrote:
Hi,

I'm planning to dockerize my sonar installation (so it will be easier to move around and test new sonar versions, mostly as a convenience for myself, it is not supposed to be universal docker container). The only problem that I can find with dockerizing sonarqube is that it uses embedded elasticsearch (which keeps data locally in the installation dir). The question is, how the elasticsearch is currently used and how it is going to be used in the future? Can I safely assume that the es is used only as a local cache for the sql database (so every time I restart sonarqube I can remove the local data safely and it will be restored, the only cost being longer startup time)? If not, then can I use external elasticsearch instance?

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/707f2f68-2842-41ee-9651-f8fc4966acc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Francis Galiegue

unread,
Oct 28, 2015, 6:21:52 AM10/28/15
to SonarQube, wszystkie.fajn...@gmail.com
Hello,

Just a clarification here:

On Tuesday, October 27, 2015 at 9:33:15 PM UTC+1, Simon Brandhof wrote:

[...] All depends on the number of issues and until v5.1 on the number of lines of code.

By "until v5.1", should it be understood "up to and including v5.1", or "up to and excluding v5.1"?

Regards

David Racodon

unread,
Oct 28, 2015, 6:23:14 AM10/28/15
to Francis Galiegue, SonarQube, wszystkie.fajn...@gmail.com
up to and including v5.1

David RACODON
Freelance QA Consultant

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages