which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
what are you trying to achieve
It is an upgrade to v9.8.
what have you tried so far to achieve this
Gone through release notes(9.8) which says that v9.8 supports only postgreSQL >= 11 and support for postgreSQL 9.6 is dropped. We are in postgreSQL9.6. If I understood the upgrade process correctly, I need to do the following steps.
Migrate postgreSQL 9.6 data to postgreSQL 11
Test SonarQube 9.5 able to connect the updated DB (not sure if SonarQube 9.5 has a database driver to connect to postgreSQL11 -please suggest)
Upgrade SonarQube 9.5 to 9.8
Please let me know if any other steps I need to consider during upgrade.
We have did the upgrade of DB to postgresql11 and it is working. For performance VACCUM was run on database. Looks it improved. But still for some projects it is taking more time than it took while we were in postgreSQL9.6. Like the ones finished in 5 mins was waiting for 30 mins to finish the execution and times out. I am thinking of two possible scenarios causing a performance issue.
1.Our current db cluster is a Patroni cluster which sits behind an A10 load balancer. Does Sonarqube fully supports this kind of backend. Is there any more config required?
( PS: To address the timeouts we moved away from A10 and directly pointed to the databaseURL which fixed the issue temporarily. But we want to put the loadbalancer back into action.)
2. Would a db upgrade cause any re-indexing in Elastic search of sonar. Do I need to do any specific action on ES engine after upgrade.
My sincere apologies for not responding to you after the upgrade. Appreciate your guidance on this.