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

Master Node rejoin as master after some transactions and there is data loss.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • 6.4.0
    • 6.4.2
    • mariadbmon
    • None

    Description

      I'm using MariaDB Server 10.6.8

      (1) Start a Fresh new cluster Server 1 = master, Server2,3= Slave
      (2) Bring Master Down (without having done any transactions)
      (3) Server 2 gets promoted to Master
      (4) Perform a couple of transactions
      (5) Bring Server 2 and 3 down
      (6) Bring up Server 1
      (7) Bring up Server 2 and 3

      • Auto failover and auto rejoin are enabled
      • I'm using MaxScale

      Server 1 became master and Server 2 & 3 are not synced.

      How do I deal with this situation?

      Is it possible to check the GTID before promoting to master? So I can make sure that the node that was the last master should become master again.

      Attachments

        Activity

          People

            esa.korhonen Esa Korhonen
            myali Mohammed Y ALALI
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.