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

Standalone master loses master status

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.2.11
    • 2.2.13
    • mariadbmon
    • None

    Description

      With a three-node setup of servers A, B and C with A being the initial master, a sequence of failovers from A → B → C will result in C being assigned as a standalone master. When B is restarted, C will lose the Master status and both B and C will end up in Running state.

      The expected behavior would be that C remains as the master and B rejoins as a slave.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 3d
                3d

                Git Integration

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