| 2014-09-08 22:00:37 |
Doug Barth |
bug |
|
|
added bug |
| 2014-09-16 12:32:33 |
Valerii Kravchuk |
nominated for series |
|
percona-xtradb-cluster/5.5 |
|
| 2014-09-16 12:32:33 |
Valerii Kravchuk |
bug task added |
|
percona-xtradb-cluster/5.5 |
|
| 2014-09-16 12:32:33 |
Valerii Kravchuk |
nominated for series |
|
percona-xtradb-cluster/5.6 |
|
| 2014-09-16 12:32:33 |
Valerii Kravchuk |
bug task added |
|
percona-xtradb-cluster/5.6 |
|
| 2014-09-16 16:04:33 |
Teemu Ollakka |
bug task added |
|
codership-mysql |
|
| 2014-09-16 16:04:50 |
Teemu Ollakka |
nominated for series |
|
codership-mysql/5.6 |
|
| 2014-09-16 16:04:50 |
Teemu Ollakka |
bug task added |
|
codership-mysql/5.6 |
|
| 2014-09-16 16:04:50 |
Teemu Ollakka |
nominated for series |
|
codership-mysql/5.5 |
|
| 2014-09-16 16:04:50 |
Teemu Ollakka |
bug task added |
|
codership-mysql/5.5 |
|
| 2014-09-24 07:22:55 |
Miguel Angel Nieto |
codership-mysql/5.5: status |
New |
Incomplete |
|
| 2014-09-24 07:23:10 |
Miguel Angel Nieto |
percona-xtradb-cluster/5.6: status |
New |
Incomplete |
|
| 2014-09-24 07:23:13 |
Miguel Angel Nieto |
codership-mysql/5.6: status |
New |
Incomplete |
|
| 2014-09-24 07:24:18 |
Miguel Angel Nieto |
percona-xtradb-cluster/5.5: status |
New |
Incomplete |
|
| 2014-09-24 07:46:50 |
Miguel Angel Nieto |
bug |
|
|
added subscriber Miguel Angel Nieto |
| 2014-09-29 16:29:21 |
Doug Barth |
attachment added |
|
my.cnf https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1366997/+attachment/4219302/+files/my.cnf |
|
| 2014-10-02 08:45:35 |
Miguel Angel Nieto |
codership-mysql/5.5: status |
Incomplete |
Confirmed |
|
| 2014-10-02 08:45:39 |
Miguel Angel Nieto |
percona-xtradb-cluster/5.5: status |
Incomplete |
Confirmed |
|
| 2014-10-02 09:12:39 |
Miguel Angel Nieto |
codership-mysql/5.6: status |
Incomplete |
Confirmed |
|
| 2014-10-02 09:12:42 |
Miguel Angel Nieto |
percona-xtradb-cluster/5.6: status |
Incomplete |
Confirmed |
|
| 2014-10-14 08:15:26 |
Mario Splivalo |
bug |
|
|
added subscriber Mario Splivalo |
| 2014-11-21 03:08:03 |
Raghavendra D Prabhu |
percona-xtradb-cluster/5.5: milestone |
|
future-5.5 |
|
| 2014-11-21 03:08:05 |
Raghavendra D Prabhu |
percona-xtradb-cluster/5.6: milestone |
|
5.6.21-25.8 |
|
| 2014-11-22 22:01:50 |
Brad Jorgensen |
bug |
|
|
added subscriber Brad Jorgensen |
| 2014-11-25 07:46:31 |
Raghavendra D Prabhu |
percona-xtradb-cluster/5.6: status |
Confirmed |
Fix Committed |
|
| 2014-11-25 15:53:10 |
Hrvoje Matijakovic |
percona-xtradb-cluster/5.6: status |
Fix Committed |
Fix Released |
|
| 2014-12-02 09:31:37 |
Yaguang Tang |
bug task added |
|
percona-server-5.5 (Ubuntu) |
|
| 2014-12-02 09:31:53 |
Yaguang Tang |
percona-server-5.5 (Ubuntu): assignee |
|
Yaguang Tang (heut2008) |
|
| 2014-12-02 09:32:28 |
Yaguang Tang |
bug task deleted |
percona-server-5.5 (Ubuntu) |
|
|
| 2014-12-02 12:43:29 |
Jorge Niedbalski |
tags |
|
cts |
|
| 2014-12-05 08:17:46 |
Yaguang Tang |
description |
We (PagerDuty) have experienced on multiple occasions duplicate entry errors on the primary key for some tables after our cluster's size changes. In the cases we have experienced so far, this is when gracefully adding or removing a node to vertically scale the nodes in the cluster. We don't experience a total failure of all transactions. Instead, a small subset error out. In some cases, the problem corrects itself, but several times now we have had the errors persist for several hours. When the problem persists, we have found that restarting one of the cluster members will sometimes fix the issue.
Restarting all transactions by rebooting the application does not fix the issue. Only a restart of a cluster member can eventually solve the problem.
Here are the packages we are running
ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.1.9-744-1.lucid Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-client-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database common files (e.g. /e
ii percona-xtradb-cluster-galera-2.x 188.lucid Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database server binaries
Here is an example error that we see.
Duplicate entry '623287' for key 'PRIMARY'
That error will be seen for multiple tables, and sometimes again for the same table.
Please let me know what additional information can help. The MySQL error log doesn't appear to have any interesting details in it (just node join and leave events) but I would be glad to pass it along if you think it would be helpful. |
[Impact]
* Duplicate entry errors on the primary key for tables occurs, data
can't be added to DB correctly and in time.
[Test Case]
* Prepare a .sql file full of INSERT queries:
INSERT INTO test.t VALUES(NULL,"miguel");
that line million of times.
* Start a 3 node clusters.
* Load the data on node 1 (if you do several times in parallel you will get the error sooner): cat data.sql | mysql
* Restart node2 and wait until MySQL is running.
* Restart node3 and wait until MySQL is running.
* Repeat step 4 and 5 several times (sometimes lot of restarts are needed, sometimes just a few) and the node1 load will fail with duplicate key entry.
[Regression Potential]
* The patch to fix this issue is backported from a nearest version 5.6.
[Other Info]
We (PagerDuty) have experienced on multiple occasions duplicate entry errors on the primary key for some tables after our cluster's size changes. In the cases we have experienced so far, this is when gracefully adding or removing a node to vertically scale the nodes in the cluster. We don't experience a total failure of all transactions. Instead, a small subset error out. In some cases, the problem corrects itself, but several times now we have had the errors persist for several hours. When the problem persists, we have found that restarting one of the cluster members will sometimes fix the issue.
Restarting all transactions by rebooting the application does not fix the issue. Only a restart of a cluster member can eventually solve the problem.
Here are the packages we are running
ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.1.9-744-1.lucid Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-client-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database common files (e.g. /e
ii percona-xtradb-cluster-galera-2.x 188.lucid Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database server binaries
Here is an example error that we see.
Duplicate entry '623287' for key 'PRIMARY'
That error will be seen for multiple tables, and sometimes again for the same table.
Please let me know what additional information can help. The MySQL error log doesn't appear to have any interesting details in it (just node join and leave events) but I would be glad to pass it along if you think it would be helpful. |
|
| 2014-12-05 08:52:21 |
Yaguang Tang |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2014-12-09 09:59:04 |
Yaguang Tang |
attachment added |
|
fix-duplicate-primary-key.patch https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1366997/+attachment/4276825/+files/fix-duplicate-primary-key.patch |
|
| 2015-01-07 14:02:44 |
Edward Hope-Morley |
bug task added |
|
percona-cluster (Juju Charms Collection) |
|
| 2015-01-07 14:02:54 |
Edward Hope-Morley |
percona-cluster (Juju Charms Collection): assignee |
|
Edward Hope-Morley (hopem) |
|
| 2015-01-07 14:02:57 |
Edward Hope-Morley |
percona-cluster (Juju Charms Collection): status |
New |
In Progress |
|
| 2015-01-07 17:06:44 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2015-01-09 09:45:57 |
Alexey Kopytov |
percona-xtradb-cluster/5.5: assignee |
|
Alexey Kopytov (akopytov) |
|
| 2015-01-09 09:46:00 |
Alexey Kopytov |
percona-xtradb-cluster/5.5: status |
Confirmed |
Invalid |
|
| 2015-01-09 09:46:07 |
Alexey Kopytov |
percona-xtradb-cluster/5.5: status |
Invalid |
In Progress |
|
| 2015-01-09 11:46:17 |
Alexey Kopytov |
percona-xtradb-cluster/5.5: status |
In Progress |
Fix Committed |
|
| 2015-01-09 11:46:26 |
Alexey Kopytov |
branch linked |
|
lp:~akopytov/percona-xtradb-cluster/bug1366997-5.5 |
|
| 2015-01-09 11:46:44 |
Alexey Kopytov |
branch linked |
|
lp:~hopem/charms/trusty/percona-cluster/trusty-workaround-bug-1366997 |
|
| 2015-01-09 11:46:52 |
Alexey Kopytov |
branch unlinked |
lp:~hopem/charms/trusty/percona-cluster/trusty-workaround-bug-1366997 |
|
|
| 2015-01-26 11:21:11 |
Alexey Kopytov |
percona-xtradb-cluster/5.5: status |
Fix Committed |
Fix Released |
|
| 2015-02-10 12:10:59 |
Mario Splivalo |
branch linked |
|
lp:~mariosplivalo/charms/trusty/percona-cluster/lp1366997-workaround |
|
| 2015-02-11 23:19:25 |
Launchpad Janitor |
branch linked |
|
lp:~openstack-charmers/charms/trusty/percona-cluster/next |
|
| 2015-03-06 16:09:42 |
Raghavendra D Prabhu |
percona-xtradb-cluster/5.5: milestone |
future-5.5 |
5.5.41-25.11 |
|
| 2015-03-17 11:06:45 |
Edward Hope-Morley |
bug task added |
|
percona-cluster (Ubuntu) |
|
| 2015-03-17 11:07:51 |
Launchpad Janitor |
percona-xtradb-cluster-5.5 (Ubuntu): status |
New |
Confirmed |
|
| 2015-03-17 11:07:51 |
Edward Hope-Morley |
affects |
percona-cluster (Ubuntu) |
percona-xtradb-cluster-5.5 (Ubuntu) |
|
| 2015-03-17 11:08:34 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu): status |
New |
Confirmed |
|
| 2015-03-23 22:19:16 |
Mario Splivalo |
attachment added |
|
trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu1.14.04.2.debdiff https://bugs.launchpad.net/codership-mysql/+bug/1366997/+attachment/4353910/+files/trusty_percona-xtradb-cluster-5.5_5.5.37-25.10%2Bdfsg-0ubuntu1.14.04.2.debdiff |
|
| 2015-03-24 16:41:08 |
Chris J Arges |
nominated for series |
|
Ubuntu Trusty |
|
| 2015-03-24 16:41:08 |
Chris J Arges |
bug task added |
|
percona-xtradb-cluster-5.5 (Ubuntu Trusty) |
|
| 2015-03-24 17:00:26 |
Robie Basak |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2015-03-26 14:16:51 |
Alex Yurchenko |
codership-mysql/5.6: status |
Confirmed |
Fix Released |
|
| 2015-05-06 08:04:24 |
Edward Hope-Morley |
percona-cluster (Juju Charms Collection): assignee |
Edward Hope-Morley (hopem) |
Mario Splivalo (mariosplivalo) |
|
| 2015-05-06 08:06:04 |
Edward Hope-Morley |
percona-cluster (Juju Charms Collection): milestone |
|
15.04 |
|
| 2015-05-06 08:06:06 |
Edward Hope-Morley |
percona-cluster (Juju Charms Collection): status |
In Progress |
Fix Released |
|
| 2015-08-27 06:48:34 |
Ray Wang |
bug |
|
|
added subscriber Ray Wang |
| 2017-06-07 13:35:01 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu): assignee |
|
Mario Splivalo (mariosplivalo) |
|
| 2017-06-07 13:35:07 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu Trusty): assignee |
|
Mario Splivalo (mariosplivalo) |
|
| 2017-06-07 13:35:16 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2017-06-07 13:35:27 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-06-07 13:35:34 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu Trusty): status |
Confirmed |
In Progress |
|
| 2017-06-08 00:51:02 |
Ray Wang |
removed subscriber Ray Wang |
|
|
|
| 2017-06-08 23:23:44 |
Christian Ehrhardt |
removed subscriber Ubuntu Server Team |
|
|
|
| 2017-06-09 12:19:41 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2017-06-13 10:01:30 |
Edward Hope-Morley |
tags |
cts |
cts sts sts-sru-needed |
|
| 2017-06-13 19:29:37 |
Eric Desrochers |
percona-xtradb-cluster-5.5 (Ubuntu Trusty): importance |
Undecided |
Medium |
|
| 2017-06-15 13:34:16 |
Mario Splivalo |
attachment removed |
trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu1.14.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.5/+bug/1366997/+attachment/4353910/+files/trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu1.14.04.2.debdiff |
|
|
| 2017-06-19 13:55:06 |
Mario Splivalo |
attachment added |
|
trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.3.debdiff https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.5/+bug/1366997/+attachment/4898590/+files/trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.3.debdiff |
|
| 2017-06-19 13:57:10 |
Mario Splivalo |
attachment removed |
trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.3.debdiff https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.5/+bug/1366997/+attachment/4898590/+files/trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.3.debdiff |
|
|
| 2017-06-19 14:00:14 |
Mario Splivalo |
attachment added |
|
trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.4.debdiff https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.5/+bug/1366997/+attachment/4898591/+files/trusty_percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.4.debdiff |
|
| 2017-06-19 15:22:16 |
Eric Desrochers |
description |
[Impact]
* Duplicate entry errors on the primary key for tables occurs, data
can't be added to DB correctly and in time.
[Test Case]
* Prepare a .sql file full of INSERT queries:
INSERT INTO test.t VALUES(NULL,"miguel");
that line million of times.
* Start a 3 node clusters.
* Load the data on node 1 (if you do several times in parallel you will get the error sooner): cat data.sql | mysql
* Restart node2 and wait until MySQL is running.
* Restart node3 and wait until MySQL is running.
* Repeat step 4 and 5 several times (sometimes lot of restarts are needed, sometimes just a few) and the node1 load will fail with duplicate key entry.
[Regression Potential]
* The patch to fix this issue is backported from a nearest version 5.6.
[Other Info]
We (PagerDuty) have experienced on multiple occasions duplicate entry errors on the primary key for some tables after our cluster's size changes. In the cases we have experienced so far, this is when gracefully adding or removing a node to vertically scale the nodes in the cluster. We don't experience a total failure of all transactions. Instead, a small subset error out. In some cases, the problem corrects itself, but several times now we have had the errors persist for several hours. When the problem persists, we have found that restarting one of the cluster members will sometimes fix the issue.
Restarting all transactions by rebooting the application does not fix the issue. Only a restart of a cluster member can eventually solve the problem.
Here are the packages we are running
ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.1.9-744-1.lucid Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-client-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database common files (e.g. /e
ii percona-xtradb-cluster-galera-2.x 188.lucid Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database server binaries
Here is an example error that we see.
Duplicate entry '623287' for key 'PRIMARY'
That error will be seen for multiple tables, and sometimes again for the same table.
Please let me know what additional information can help. The MySQL error log doesn't appear to have any interesting details in it (just node join and leave events) but I would be glad to pass it along if you think it would be helpful. |
[Impact]
* Duplicate entry errors on the primary key for tables occurs, data
can't be added to DB correctly and in time.
[Test Case]
* Prepare a .sql file full of INSERT queries:
INSERT INTO test.t VALUES(NULL,"miguel");
that line million of times.
* Start a 3 node clusters.
* Load the data on node 1 (if you do several times in parallel you will get the error sooner): cat data.sql | mysql
* Restart node2 and wait until MySQL is running.
* Restart node3 and wait until MySQL is running.
* Repeat step 4 and 5 several times (sometimes lot of restarts are needed, sometimes just a few) and the node1 load will fail with duplicate key entry.
[Regression Potential]
* The patch to fix this issue is backported from a nearest version 5.6.
[Other Info]
* For Ubuntu SRU verification team :
https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1366997/comments/21
We (PagerDuty) have experienced on multiple occasions duplicate entry errors on the primary key for some tables after our cluster's size changes. In the cases we have experienced so far, this is when gracefully adding or removing a node to vertically scale the nodes in the cluster. We don't experience a total failure of all transactions. Instead, a small subset error out. In some cases, the problem corrects itself, but several times now we have had the errors persist for several hours. When the problem persists, we have found that restarting one of the cluster members will sometimes fix the issue.
Restarting all transactions by rebooting the application does not fix the issue. Only a restart of a cluster member can eventually solve the problem.
Here are the packages we are running
ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.1.9-744-1.lucid Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-client-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database common files (e.g. /e
ii percona-xtradb-cluster-galera-2.x 188.lucid Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database server binaries
Here is an example error that we see.
Duplicate entry '623287' for key 'PRIMARY'
That error will be seen for multiple tables, and sometimes again for the same table.
Please let me know what additional information can help. The MySQL error log doesn't appear to have any interesting details in it (just node join and leave events) but I would be glad to pass it along if you think it would be helpful. |
|
| 2017-06-19 15:24:50 |
Eric Desrochers |
tags |
cts sts sts-sru-needed |
cts sts sts-sponsor-done sts-sru-needed |
|
| 2017-06-19 16:06:55 |
Łukasz Zemczak |
percona-xtradb-cluster-5.5 (Ubuntu Trusty): status |
In Progress |
Fix Committed |
|
| 2017-06-19 16:06:59 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2017-06-19 16:07:05 |
Łukasz Zemczak |
tags |
cts sts sts-sponsor-done sts-sru-needed |
cts sts sts-sponsor-done sts-sru-needed verification-needed |
|
| 2017-06-19 18:47:30 |
Eric Desrochers |
description |
[Impact]
* Duplicate entry errors on the primary key for tables occurs, data
can't be added to DB correctly and in time.
[Test Case]
* Prepare a .sql file full of INSERT queries:
INSERT INTO test.t VALUES(NULL,"miguel");
that line million of times.
* Start a 3 node clusters.
* Load the data on node 1 (if you do several times in parallel you will get the error sooner): cat data.sql | mysql
* Restart node2 and wait until MySQL is running.
* Restart node3 and wait until MySQL is running.
* Repeat step 4 and 5 several times (sometimes lot of restarts are needed, sometimes just a few) and the node1 load will fail with duplicate key entry.
[Regression Potential]
* The patch to fix this issue is backported from a nearest version 5.6.
[Other Info]
* For Ubuntu SRU verification team :
https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1366997/comments/21
We (PagerDuty) have experienced on multiple occasions duplicate entry errors on the primary key for some tables after our cluster's size changes. In the cases we have experienced so far, this is when gracefully adding or removing a node to vertically scale the nodes in the cluster. We don't experience a total failure of all transactions. Instead, a small subset error out. In some cases, the problem corrects itself, but several times now we have had the errors persist for several hours. When the problem persists, we have found that restarting one of the cluster members will sometimes fix the issue.
Restarting all transactions by rebooting the application does not fix the issue. Only a restart of a cluster member can eventually solve the problem.
Here are the packages we are running
ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.1.9-744-1.lucid Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-client-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database common files (e.g. /e
ii percona-xtradb-cluster-galera-2.x 188.lucid Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database server binaries
Here is an example error that we see.
Duplicate entry '623287' for key 'PRIMARY'
That error will be seen for multiple tables, and sometimes again for the same table.
Please let me know what additional information can help. The MySQL error log doesn't appear to have any interesting details in it (just node join and leave events) but I would be glad to pass it along if you think it would be helpful. |
[Impact]
* Duplicate entry errors on the primary key for tables occurs, data
can't be added to DB correctly and in time.
[Test Case]
* Prepare a .sql file full of INSERT queries:
INSERT INTO test.t VALUES(NULL,"miguel");
that line million of times.
* Start a 3 node clusters.
* Load the data on node 1 (if you do several times in parallel you will get the error sooner): cat data.sql | mysql
* Restart node2 and wait until MySQL is running.
* Restart node3 and wait until MySQL is running.
* Repeat step 4 and 5 several times (sometimes lot of restarts are needed, sometimes just a few) and the node1 load will fail with duplicate key entry.
[Regression Potential]
* The patch to fix this issue is backported from a nearest version 5.6.
* There is failed build for powerpc architecture, but this was not introduced by this change - one can check that this has been like this in previous releases too:
https://launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.5
If you expand previous versions (14.04.1 and 14.04.2) you can see that the build was failing for powerpc.
Buildlog:
https://launchpadlibrarian.net/324600505/buildlog_ubuntu-trusty-powerpc.percona-xtradb-cluster-5.5_5.5.37-25.10+dfsg-0ubuntu0.14.04.4_BUILDING.txt.gz
[Other Info]
* For Ubuntu SRU verification team :
https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1366997/comments/21
We (PagerDuty) have experienced on multiple occasions duplicate entry errors on the primary key for some tables after our cluster's size changes. In the cases we have experienced so far, this is when gracefully adding or removing a node to vertically scale the nodes in the cluster. We don't experience a total failure of all transactions. Instead, a small subset error out. In some cases, the problem corrects itself, but several times now we have had the errors persist for several hours. When the problem persists, we have found that restarting one of the cluster members will sometimes fix the issue.
Restarting all transactions by rebooting the application does not fix the issue. Only a restart of a cluster member can eventually solve the problem.
Here are the packages we are running
ii percona-toolkit 2.2.7 Advanced MySQL and system command-line tools
ii percona-xtrabackup 2.1.9-744-1.lucid Open source backup tool for InnoDB and XtraDB
ii percona-xtradb-cluster-client-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database client binaries
ii percona-xtradb-cluster-common-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database common files (e.g. /e
ii percona-xtradb-cluster-galera-2.x 188.lucid Galera components of Percona XtraDB Cluster
ii percona-xtradb-cluster-server-5.5 5.5.37-25.10-756.lucid Percona XtraDB Cluster database server binaries
Here is an example error that we see.
Duplicate entry '623287' for key 'PRIMARY'
That error will be seen for multiple tables, and sometimes again for the same table.
Please let me know what additional information can help. The MySQL error log doesn't appear to have any interesting details in it (just node join and leave events) but I would be glad to pass it along if you think it would be helpful. |
|
| 2017-06-23 16:41:47 |
Mario Splivalo |
tags |
cts sts sts-sponsor-done sts-sru-needed verification-needed |
cts sts sts-sponsor-done sts-sru-needed verification-done |
|
| 2017-06-27 14:18:04 |
Łukasz Zemczak |
tags |
cts sts sts-sponsor-done sts-sru-needed verification-done |
cts sts sts-sponsor-done sts-sru-needed verification-done-trusty |
|
| 2017-06-28 00:17:19 |
Launchpad Janitor |
percona-xtradb-cluster-5.5 (Ubuntu Trusty): status |
Fix Committed |
Fix Released |
|
| 2017-06-28 00:17:26 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-06-28 00:22:42 |
Ubuntu Foundations Team Bug Bot |
tags |
cts sts sts-sponsor-done sts-sru-needed verification-done-trusty |
cts patch sts sts-sponsor-done sts-sru-needed verification-done-trusty |
|
| 2017-06-28 00:22:51 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2017-06-29 13:10:10 |
Eric Desrochers |
tags |
cts patch sts sts-sponsor-done sts-sru-needed verification-done-trusty |
cts patch sts sts-sponsor-done sts-sru-done verification-done-trusty |
|
| 2017-08-29 07:51:20 |
Mario Splivalo |
percona-xtradb-cluster-5.5 (Ubuntu): status |
In Progress |
Fix Released |
|
