Does SonarQube Compute Engine ensure data atomicity during task cancellation?

Cancellation Atomicity in the Compute Engine

No, the SonarQube Compute Engine (CE) does not ensure end-to-end data atomicity for an entire analysis task upon cancellation. A cancellation request does not trigger a global transactional rollback of all data persisted during that task's lifecycle.

How Cancellation Works

Cancellation in the CE is a cooperative process rather than a hard process kill. When a user cancels a task via the UI or API, the system updates the task status to CANCELLED in the database. The worker thread processing the analysis checks for this status change at specific intervals or between execution steps.

Likely Behavior and Data Risks

Because the Compute Engine persists analysis results in multiple stages and separate database transactions, the following behaviors are expected:

• Partial Persistence: If a worker is interrupted after completing a persistence step but before the entire task is finished, the data committed during that step remains in the database.
• Orphaned Records: While the task is marked as CANCELLED, intermediate measures or issues may have already been committed to the database, potentially leaving fragments of an incomplete analysis.
• Non-Atomic Side Effects: External actions, such as triggering webhooks or updating ALM decorations, occur outside the CE's internal database transactions and cannot be rolled back.

SonarQube generally relies on the idempotency of subsequent analyses to overwrite or supersede incomplete states rather than implementing a complex compensating rollback mechanism for every cancelled task.

Verification Steps

To determine if a specific cancellation left the project in an inconsistent state, follow these steps:

1. Log Analysis: Search the ce.log for the specific Task UUID to identify the last successfully completed step before the cancellation was processed.
2. State Comparison: Check the project's measures and issues via the API to see if a new snapshot was created or if partial data is visible despite the CANCELLED status.
3. Idempotency Test: Rerun the analysis for the same project. A successful subsequent run should resolve any partial states by providing a complete, updated snapshot.

Note: To provide a more precise recommendation, please specify the SonarQube version and whether you are using the Data Center Edition, as clustering may affect how task states are synchronized across nodes.