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

cooperative_monitoring secondary MaxScale can ignore failover by primary MaxScale

    XMLWordPrintable

Details

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

    Description

      Primary A, replicas B & C. Replica B goes down. Then later, A goes down. MXS1 does failover. MXS2 does not abandon A as it still sees B replicating from it (using old data).

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            esa.korhonen Esa Korhonen
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.