** Description changed: [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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366997 Title: Duplicate entry error for primary key following cluster size change To manage notifications about this bug go to: https://bugs.launchpad.net/codership-mysql/+bug/1366997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
