Elastic Search Index

SonarQube Server / Community Build
,
1

We are currently running Sonarqube 8.9 LTS, i would to know, if there is a easy way to delete Elastic search index automatically.

If there is a suggestion for Life cycle managemnt Policy then i imagine we cannot use it
, because we have specific triggers. Usually the restore of a database dump ,while elastic search is shutdown.

Regards

2

Hi,

Could you share why you want to regularly delete the ES indices? It’s not recommended…

 
Ann

3

Hello,
Not regularly , but if we restart the pod or create or it crashes
.
Then we have to manually delete the index.

4

i had an idea of using Curl command in Image build , so everytime a new pod will run it should first delete the files. But its complicated to make it automatic as the file names may differ in future.
or is there a way using Curl command to automate it .

5

Hi,

I guess you’ve enabled persistence? It’s not recommended because it can result in corrupt ES indices. Maybe turn it back off & the problem just goes away?

 
Ann

6

Sorry i guess i cannot explain you in short description.
So i try again, we are currently running Sonarqube 8.9 LTS, on Openshift which is bound to a PV.
The Es data get stores in /opt/sonarqube/data in PV under “es7” currently. So everytime an event happen, we have to manually shut the Sonarqube pod, delete the “es*” directory and restart the pod.

so to avoid this basic manual process, i am looking for a automate process or is it also possible creating a Jenkins job for automatically deleting “es” folder in PV.
If you need more info please let me know .
Regards

9

Hi,

As Ann mentioned, have you tried disabling persistence?
That should solve your issue.

Jay

10

@Jeremy_Davis How do i disable it ?
Sorry i guess i didnt get it.
Pardon me i am new Sonarqube user.
Can you please elaborate or share some references ?
Is it also possible to create a Jenkins pipeline , which can access the Volume, Delete the ESI diretory, unless doing it manually
If yes please suggest a way.

Regards

11

Sonarqube showing incorrect count of issues on dashboard - SonarQube - Sonar Community (sonarsource.com)
i found a topic where they suggested the same option of deleting /data/es and restarting the server.
Julien Lancelot and Nicolas Bontoux suggested the way .
so i would like to know a way to automate this process, rather than doing it manually.
Regards

12

Can you guide me a automatic way to delete data/es ?
we are facing same problem and we have to manually delete it.
i would like to automate the process .
Please guide me and some sample would be nice .
Regards

13

The documentation that Ann shared explains it.

It’s in values.yaml:

 persistence:
   enabled: false
1 Like
14

where can i find this value ?
Can you please redirect me to the location.
Regards

15

Hi,

You need to look in your own files for this value. Maybe just do a text search?

 
Ann

17

Per

Per1
Per11176Ă—501 17.8 KB

This is where i find something similar.
I cannot find the persistence:
enabled: false/true anywhere .
Its our Template for Openshift
Regards

18

Hi,

Maybe take a look at your _Persistent_VolumeClaim?

 
Ann

19

okay i guess in my case it " cpr-tmp volume"
so i disable it and now it worked .
so thank you all for pointing the error guys.
Cheers