Post Sonarqube Migration Reindex taking +20hrs

Hi Pierre,

Can you tell us more about your experience with Migrating/Upgrading that 500gb database? How big were your provisioned instances and what was your Sonar configuration? I ask because currently our 7gb database is still running it’s migration/upgrade at 14hrs.

We also noticed this JIRA ticket which you seem to have been the main driver of, can we ask you some questions about it?
https://jira.sonarsource.com/browse/MMF-1671

  1. Your comment says the data utilized 5.8k projects, how was this number derived? Based on API calls our production instance looks too have 78k, which I find unbelievable.
  2. During our non-prod upgrade testing we are not seeing IO, memory or CPU being utilized heavily on the Sonar instance. Is this because all the work is performed on the database? And if so did you have any database tweaks that sped up this process noticeably?

Thanks again,
Brandon and Team