| Edition | Developer |
|---|---|
| Lines of Code | 4969090 |
| Docker | No |
| High Availability | No |
| Official Distribution | Yes |
| Force authentication | Yes |
| Home Dir | /data/sonarqube-9.9.1-developer |
| Data Dir | /data/sonarqube-9.9.1-developer/data |
| Temp Dir | /data/sonarqube-9.9.1-developer/temp |
| Processors | 4 |
Database
| Database | Oracle |
|---|---|
| Database Version | Oracle Database 19c Standard Edition 2 Release 19.0.0.0.0 - Production Version 19.11.0.0.0 |
| URL | jdbc:oracle:thin:@aaaaa.xxxx.be:1521:TOOL |
| Driver | Oracle JDBC driver |
| Driver Version | 21.8.0.0.0 |
| Default transaction isolation | TRANSACTION_READ_COMMITTED |
Issue:
IT managing SonarQube and its DB is using archive logging so we can do a point in time restore. This week the DB ran quickly out of disk space because the archive logs grew fast.
Investigation of the DB transactions showed alot of inserts and deletes in the live_measures table.
In about 2 hours 20 minutes, there are over 1.2 million writes in this table.
Questions:
- Are there config settings to reduce the number of insert/deletes in the live_measures table?
- Are you considering code optimizations in future Sonar versions?
- Can you explain what the purpose is of this table? What common actions generate writes in this table?
