Kubernetes pod dies with memory leak every now and then

SonarQube Server / Community Build
1

Problem:
Sonarqube pod gets killed every now and then. This makes it unavailable for scans most of the time and not helping team building quality code.

Sonarqube 8.9.1 CE and Sonar-scanner 2.13 Jenkins Plugin

When the logs are analyzed, this is the last set of lines in Compute engine:

2021.07.16 03:32:19 INFO  ce[][o.s.c.t.CeProcessingSchedulerImpl] Gracefully stopping workers...
2021.07.16 03:32:29 WARN  ce[][o.s.c.t.CeProcessingSchedulerExecutorServiceImpl] Pool CeProcessingSchedulerExecutorServiceImpl did not terminate
2021.07.16 03:32:29 INFO  ce[][o.s.ce.app.CeServer] Compute Engine is stopped
2021.07.16 03:32:44 ERROR ce[][o.s.c.t.CeWorkerImpl] Failed to pop the queue of analysis reports
org.apache.ibatis.exceptions.PersistenceException: 
### Error updating database.  Cause: java.sql.SQLException: Data source is closed

sonar-scanner
sonar.projectKey=[PROJECT-FOLDER] 
sonar.sources=one, two, three
sonar.exclusions=**/*.js,**/*.rb,**/*.css,**/*.scss,**/*.html,**/*.php,**/*.xml,**/*.java
sonar.python.coverage.reportPaths=suite*/cover*.xml

Its failing due to sonarqube pod is getting killed and the server isn't available for scan uploads.```



Thanks in advance
2

Hi @Dharmender_Kumar ,

This looks more related to the database than sonarqube itself. is your database crashing? Did you already investigate why the database is not available?

Regarding the memory leak; this should not be a concern. this is a warning that is thrown when the application can not terminate all started threads but as the jvm and therefore the pod is dying, this is not really a memory leak.

3

Thanks @Tobias_Trabelsi! We reduced the no. of scans to be maintained in DB retrospectively and that solved the thing.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.