Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-4053

The semaphore mechanism should automatically detect when an other semaphore is outdated and so can/should be ignored

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5
    • Component/s: Scanner
    • Labels:
      None

      Description

      This semaphore mechanism was introduced in Sonar 3.4 to prevent two analysis on the same resource (project, view, ...) to be executed at the same time. But if an analysis is unexpectedly stopped for instance by killing the java process, the semaphore remains and it's then up to the Sonar administrator to use the property 'sonar.forceAnalysis' to ignore this past outdated semaphore.

      We should prevent the Sonar administrator from having to take care about such situation by asking each alive semaphore to 'ping' the Sonar server. If a semaphore hasn't ping the Sonar server during the past X minutes we could then consider it as outdated.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              henryju OLD - Julien HENRY
              Reporter:
              freddy.mallet Freddy Mallet (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: