Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3793

Race condition in GCUpdater shutdown

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 6.1.2
    • Fix Version/s: 6.2.0
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-141

      Description

      The test_filter test fails occasionally with a hang. The hang appears to be caused by the thread doing the updates not being in sync with the thread that starts it. Inspecting the hanging test with a debugger shows that the m_running variable was the probable culprit: if the thread that does the updates hasn't had the chance to start before a call to GCUpdater::stop() is made, the value of m_running would remain true even after the stop() call.

      In theory this can happen with smartrouter in 2.5 if a service is created and then destroyed immediately. Given the unlikely nature of it, fixing the hang in 2.5 is not required.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            nantti Niclas Antti
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.