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

alter table exchange partition is not replicated in galera cluster

Details

    Description

      Even under wsrep_osu_method=TOI, alter table TableName exchange partition P1 with table TableName_P1; is not replicated to other nodes in the cluster. The partition was exchanged on the node which issue the command, and have this line in the error log

      150124 23:46:42 [ERROR] Transaction not registered for MySQL 2PC, but transaction is active

      To replicate

      CREATE TABLE Temp.T_Test (
        `ID` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
        PRIMARY KEY (`ID`)
      ) ENGINE=InnoDB
      PARTITION BY RANGE (ID)
      (PARTITION p10 VALUES LESS THAN (10) ENGINE = InnoDB,
       PARTITION p20 VALUES LESS THAN (20) ENGINE = InnoDB,
       PARTITION pMax VALUES LESS THAN MAXVALUE ENGINE = InnoDB) ;
       
      INSERT into T_Test (ID) VALUE (9),(19);
      CREATE table Temp.T_TestP10 like Temp.T_Test;
      alter table Temp.T_TestP10  remove partitioning;
      alter table Temp.T_Test exchange partition p10 with table Temp.T_TestP10; 
      select * from Temp.T_Test;

      On node 1, the result is only one row with value 19, on all other node, the result will have two rows value 9,19.

      Attachments

        Activity

          Transition Time In Source Status Execution Times
          Nirbhay Choubey (Inactive) made transition -
          Open In Progress
          187d 9h 38m 1
          Nirbhay Choubey (Inactive) made transition -
          In Progress Closed
          5d 15h 5m 1

          People

            nirbhay_c Nirbhay Choubey (Inactive)
            leomkkwan Leo Kwan
            Votes:
            1 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.