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

Wrong master selected after restart

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • mariadbmon
    • None
    • MXS-SPRINT-244

    Description

      If cooperative monitoring is used with two MaxScales and three MariaDB servers, after a restart of one MaxScale sometimes the wrong server is selected as the master.

      Attachments

        Issue Links

          causes

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34878 Semisync recovery mode

          • Critical - Crashes, loss of data, severe memory leak.
          • Needs Feedback

          Activity

            People

              esa.korhonen Esa Korhonen
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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