Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-31905

WSREP GTID MODE is inconsistent

    XMLWordPrintable

Details

    Description

      WSREP GTID MODE is inconsistent

      When you create a Galera cluster with the following configuration according to documentation:

      # NODE 1 (m1)
      		 
      wsrep_gtid_mode=ON
      		 
      wsrep_gtid_domain_id=1111
      		 
      gtid_domain_id=2
      		 
      server_id=10999
      		 
      log_slave_updates=ON
      		 
      log_bin = /var/log/mysql/mariadb-bin-log
      		 
       
      		 
      # NODE 2 (m2)
      		 
      wsrep_gtid_mode=ON
      		 
      wsrep_gtid_domain_id=1111
      		 
      gtid_domain_id=3
      		 
      server_id=10999
      		 
      log_slave_updates=ON
      		 
      log_bin = /var/log/mysql/mariadb-bin-log
      		 
       
      		 
      # NODE 3 (m3)
      		 
      wsrep_gtid_mode=ON
      		 
      wsrep_gtid_domain_id=1111
      		 
      gtid_domain_id=4
      		 
      server_id=10999
      		 
      log_slave_updates=ON
      		 
      log_bin = /var/log/mysql/mariadb-bin-log

      Sometimes, the nodes will stay in sync. However, if the following is done:
      1) transactions run on all three nodes
      2) restart mariadb on any node
      3) restart all three nodes, using galera_new_cluster on a different node from first startup

      Then, GTIDs will become inconsistent both at the domain level and at the seq_no level.

      This is not difficult to reproduce.

      Attachments

        1. after-restart-all-three-nodes-galera-new-cluster-was-on-m2.png
          after-restart-all-three-nodes-galera-new-cluster-was-on-m2.png
          87 kB
        2. n1.cnf
          1.0 kB
        3. n2.cnf
          1.0 kB
        4. n3.cnf
          1.0 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28015 Mariabackup | GTID value is missing, Galera Cluster , adding async slave to it

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34170 table gtid_slave_pos entries never been deleted with wsrep_gtid_mode = 0

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34924 gtid_slave_pos table rows newer been deleted on non replica nodes (wsrep_gtid_mode = 1)

          • Critical - Crashes, loss of data, severe memory leak.
          • In Review

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32740 wsrep_gtid_domain_id is disregarded on any node other than bootstrapped node when the wsrep_gtid_mode is set to ON with wsrep_provider_version 26.4.14 (Galera 4)

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33610 Circular replication breaks after upgrading

          • Major - Major loss of function.
          • Open

          Activity

            People

              sysprg Julius Goryavsky
              edward Edward Stoever
              Votes:
              3 Vote for this issue
              Watchers:
              12 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.