| 2014-02-26 10:00:05 |
liuxiaocheng |
bug |
|
|
added bug |
| 2014-02-26 10:01:19 |
liuxiaocheng |
information type |
Public |
Public Security |
|
| 2014-02-26 10:01:20 |
liuxiaocheng |
information type |
Public Security |
Private Security |
|
| 2014-02-26 10:01:26 |
liuxiaocheng |
information type |
Private Security |
Public |
|
| 2014-02-26 10:02:46 |
liuxiaocheng |
description |
Server version: 5.5.34-55-log Percona XtraDB Cluster (GPL), wsrep_25.9.r3928
Description:
I build a two nodes xtradb cluster for test and they are running with the same configuration.
Table define:
mysql> show create table t2\G
*************************** 1. row ***************************
Table: t2
Create Table: CREATE TABLE `t2` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`idd` int(11) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=37 DEFAULT CHARSET=utf8 COLLATE=utf8_bin
1 row in set (0.00 sec)
Value of auto_increment is 37, execute sql：
mysql> update t2 set id=40 where id=1;
As known,the value of auto increment counter is still 37. execute sql：
mysql> replace t2 values(40,2);
Now comes the problem :On the source node ,auto increment counter's values is 41,but it still is 37 on the other nodes.
If now a insert statement execute on another node with an unspecified value for auto increment column . 38 will be allocated for new row 's auto increment column . When the counter increase up to 40,It get a error:
mysql> insert into t2(idd) values(0);
ERROR 1062 (23000): Duplicate entry '40' for key 'PRIMARY'
So,It could cause problems with different auto increment counter on the nodes in the cluster;
Some variables :
wsrep_auto_increment_control=1
innodb_autoinc_lock_mode=2
binlog_format=ROW
thanks |
Server version: 5.5.34-55-log Percona XtraDB Cluster (GPL), wsrep_25.9.r3928
Description:
I build a two nodes xtradb cluster for test and they are running with the same configuration.
Table define:
mysql> show create table t2\G
*************************** 1. row ***************************
Table: t2
Create Table: CREATE TABLE `t2` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`idd` int(11) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=37 DEFAULT CHARSET=utf8 COLLATE=utf8_bin
1 row in set (0.00 sec)
Value of auto_increment is 37, execute sql：
mysql> update t2 set id=40 where id=1;
As known,the value of auto increment counter is still 37. execute sql：
mysql> replace t2 values(40,2);
Now comes the problem :On the source node ,auto increment counter's values is 41,but it still is 37 on the other nodes.
If now a insert statement execute on another node with an unspecified value for auto increment column . 38 will be allocated for new row 's auto increment column . When the counter increase up to 40,It get a error:
mysql> insert into t2(idd) values(0);
ERROR 1062 (23000): Duplicate entry '40' for key 'PRIMARY'
So,It could cause problems with different auto increment counter on the nodes in the cluster;
Some variables :
wsrep_auto_increment_control=1
innodb_autoinc_lock_mode=2
binlog_format=ROW
thanks |
|
| 2014-02-27 17:23:12 |
Raghavendra D Prabhu |
nominated for series |
|
percona-xtradb-cluster/5.6 |
|
| 2014-02-27 17:23:12 |
Raghavendra D Prabhu |
bug task added |
|
percona-xtradb-cluster/5.6 |
|
| 2014-02-27 17:23:12 |
Raghavendra D Prabhu |
nominated for series |
|
percona-xtradb-cluster/trunk |
|
| 2014-02-27 17:23:12 |
Raghavendra D Prabhu |
bug task added |
|
percona-xtradb-cluster/trunk |
|
| 2014-02-27 17:23:20 |
Raghavendra D Prabhu |
percona-xtradb-cluster/trunk: status |
New |
Confirmed |
|
| 2014-02-27 17:23:25 |
Raghavendra D Prabhu |
percona-xtradb-cluster/5.6: milestone |
|
5.6-future |
|
| 2014-02-27 17:23:27 |
Raghavendra D Prabhu |
percona-xtradb-cluster/trunk: milestone |
|
future-5.5 |
|
| 2014-02-27 18:44:19 |
Alex Yurchenko |
bug task added |
|
codership-mysql |
|
| 2014-02-27 18:45:03 |
Alex Yurchenko |
nominated for series |
|
codership-mysql/5.5 |
|
| 2014-02-27 18:45:03 |
Alex Yurchenko |
bug task added |
|
codership-mysql/5.5 |
|
| 2014-02-27 18:45:03 |
Alex Yurchenko |
nominated for series |
|
codership-mysql/5.6 |
|
| 2014-02-27 18:45:03 |
Alex Yurchenko |
bug task added |
|
codership-mysql/5.6 |
|
| 2014-02-27 18:45:33 |
Alex Yurchenko |
codership-mysql/5.5: importance |
Undecided |
Low |
|
| 2014-02-27 18:45:37 |
Alex Yurchenko |
codership-mysql/5.6: importance |
Undecided |
Low |
|
| 2014-02-27 18:45:53 |
Alex Yurchenko |
codership-mysql/5.5: milestone |
|
5.5.36-25.10 |
|
| 2014-02-27 18:46:05 |
Alex Yurchenko |
codership-mysql/5.6: milestone |
|
5.6.16-25.5 |
|
| 2014-03-13 11:46:21 |
Alex Yurchenko |
codership-mysql/5.6: milestone |
5.6.16-25.5 |
5.6.17-25.6 |
|
| 2014-05-11 22:43:28 |
Alex Yurchenko |
codership-mysql/5.5: milestone |
5.5.37-25.10 |
5.5.37-25.11 |
|
| 2014-08-14 01:35:45 |
Hui Liu |
bug watch added |
|
http://bugs.mysql.com/bug.php?id=73563 |
|
| 2015-11-17 10:59:00 |
Krunal Bauskar |
percona-xtradb-cluster/5.5: status |
Confirmed |
Won't Fix |
|
| 2015-11-17 10:59:04 |
Krunal Bauskar |
percona-xtradb-cluster/5.6: status |
New |
Fix Committed |
|
| 2015-11-17 10:59:06 |
Krunal Bauskar |
percona-xtradb-cluster/5.5: importance |
Undecided |
Medium |
|
| 2015-11-17 10:59:09 |
Krunal Bauskar |
percona-xtradb-cluster/5.6: importance |
Undecided |
Medium |
|
