[MDEV-7501] alter table exchange partition is not replicated in galera cluster Created: 2015-01-25  Updated: 2015-08-06  Resolved: 2015-08-06

Status: Closed
Project: MariaDB Server
Component/s: Data Definition - Alter Table, Galera, Partitioning
Affects Version/s: 10.0.15-galera
Fix Version/s: 10.0.21-galera

Type: Bug Priority: Major
Reporter: Leo Kwan Assignee: Nirbhay Choubey (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Environment:

RHEL6



 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.



 Comments   
Comment by Nirbhay Choubey (Inactive) [ 2015-08-06 ]

https://github.com/MariaDB/server/commit/4c69dc8116950d6bf0b09bfbc31a86d89831a364

Generated at Thu Feb 08 07:20:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.