"alter table t truncate partition p2;" replicate failed
Bug #1219605 reported by
dennis.gao
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| MySQL patches by Codership | Status tracked in 5.6 | |||||
| 5.5 |
Fix Released
|
High
|
Seppo Jaakola | |||
| 5.6 |
Fix Released
|
High
|
Seppo Jaakola | |||
| Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
| 5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
| 5.6 |
Fix Released
|
Undecided
|
Unassigned | |||
Bug Description
galera-23.2.4 + mysql-5.
reappear it as follow steps:
1. execute on node 1, and node 2 can find the new table t:
create table t(id int) partition by range(id)(partition p1 values less than(10), partition p2 values less than(20));
2. execute on node1, success
insert into t values(1),(10);
3. so we can select the value from node1 and node2. Execute on both nodes, result is {1,10}
select * from t;
4. execute this statement on node1, and it is OK.
alter table t truncate partition p2; -- execute this statement on node1
5. but query the values, the result is not the same as expected: result from node1 is {1}, but node2 is {1,10}
select * from t;
Revision history for this message
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #1 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #2 |
Revision history for this message
| Raghavendra D Prabhu (raghavendra-prabhu) wrote | #3 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #4 |
Revision history for this message
| Seppo Jaakola (seppo-jaakola) wrote | #5 |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #6 |
To post a comment you must log in.
Noticed following (along with failure of replication of alter table).
a) No TOI is done for truncate partition but it is done for other
alter operations on the table.
b)
Also saw this in the logs: (with wsrep-debug and debug=1 in
wsrep-provider-
140226 17:09:21 [Note] WSREP: Skipping empty log_xid: (null)
140226 17:09:44 [Note] [Debug] WSREP: galera/
140226 17:09:46 [Note] [Debug] WSREP: galera/
140226 17:10:15 [Note] WSREP: Skipping empty log_xid: (null)
140226 17:10:16 [Note] [Debug] WSREP: galera/
140226 17:11:23 [Note] [Debug] WSREP: galera/