it is showing successful but pipeline is failing because of cancellation of pipeline due to awaiting response. in the administration it took 1hr13min
attaching both the screenshots here below
yeah its taking so long. and following are the details you asked for
SonarQube ID information
Server ID: 716787E2-AXSWc1HsswF2qoUkq2lx
Version: 8.9.6.50800
DB configuration - Standard S1: 20 DTUs
App service plan - ASP-Sonarqube (B2: 1)
The Standard S0, S1 and S2 tiers provide less than one vCore (CPU).
…
Regarding data storage, the Standard S0 and S1 service tiers are placed on Standard Page Blobs. Standard Page Blobs use hard disk drive (HDD)-based storage media and are best suited for development, testing, and other infrequently accessed workloads that are less sensitive to performance variability.
I would suggest scaling your database to see if the performance improves.
Apparently, if in SonarQube the background tasks take too long, it indicates a DB problem because SonarQube relies on the DB performance.
Our Azure’s DB dashboard showed that the DB IOPS were > 90% last week.
Our Datadog metrics showed that last week processing_time & process_pending_time had an unusually high peak.
We are using Azure Postgresql DB General Purpose, 2 vCore(s), 50 GB. 68% of the storage was used. The IOPS scale with the provided storage size in a ratio of 3:1.
What did you change?
We scaled up the DB to 100GB, we now have 300IOPS instead of 150IOPS according to the Azure docs.
The problem still occurs in our pipelines, is this a bug?