Must-share information (formatted with Markdown):
Deployed via docker container
Increased the size of the DB hosting sonarqube.
Current combing logs for any warning about missing indexes.
AWS upgraded our postgresql instance this morning with a major rev (10 → 12) this has caused sonarqube performance to begin to fail. Builds that are trying to reach out for their respective rules/quality gates are failing to get a response from the sonarqube server and timing out.
The database shows a drastically increasing amount of CPU in use. We doubled the size of the database but it’s still burning through all available CPU.
The UI is still functional and works well navigating through the product. It’s our build process that’s stuck at the moment trying to scan code.
Any guidance is appreciated here.