Percona is glad to announce the release of Percona XtraDB Cluster on January 30th, 2013. Binaries are available from downloads area or from our software repositories.
Bugs fixed:
- In some cases when node is recovered variable
threads_runningwould become huge. Bug fixed #1040108 (Teemu Ollakka). - Variable
wsrep_defaults_filewould be set up to the value in the last configuration file read. Bug fixed by keeping the value found in the top configuration file. Bug fixed #1079892 (Alex Yurchenko). - Variable
wsrep_node_namewas initialized before theglob_hostname, which lead to empty value forwsrep_node_nameif it wasn’t set explicitly. Bug fixed #1081389 (Alex Yurchenko). - Running
FLUSH TABLES WITH READ LOCKwhen slave applier needed to abort transaction that is on the way, caused the deadlock situation. Resolved by grabbing Global Read Lock before pausing wsrep provider. Bug fixed #1083162 (Teemu Ollakka). - Percona XtraDB Cluster would crash when processing a delete for a table with foreign key constraint. Bug fixed #1078346 (Seppo Jaakola).
- When variable
innodb_support_xawas set to 0, wsrep position wasn’t stored into the InnoDB tablespace. Bug fixed #1084199 (Teemu Ollakka). - Using XtraBackup for State Snapshot Transfer would fail due to mktemp error. Bug fixed #1080829 (Alex Yurchenko).
- XtraBackup donor would run XtraBackup indefinitely if the xtrabackup
--tmpdirwas on tmpfs. Bug fixed #1086978 (Alex Yurchenko). - In some cases non-uniform foreign key reference could cause a slave crash. Fixed by using primary key of the child table when appending exclusive key for cascading delete operation. Bug fixed #1089490 (Seppo Jaakola).
- Percona XtraDB Cluster would crash when
binlog_formatwas set toSTATEMENT. This was fixed by introducing the warning message. Bug fixed #1088400 (Seppo Jaakola). - An explicitly set
wsrep_node_incoming_addressmight make“SHOW STATUS LIKE 'wsrep_incoming_addresses';”return the address without the port number. Bug fixed #1082406 (Alex Yurchenko). - Percona XtraDB Cluster would crash if the node’s own address would be specified in the
wsrep_cluster_addressvariable. Bug fixed #1099413 (Alexey Yurchenko). - When installing from yum repository,
Percona-XtraDB-Cluster-serverandPercona-XtraDB-Cluster-clientwould conflict withmysqlandmysql-serverpackages. Bug fixed #1087506 (Ignacio Nin).
Other bug fixes: bug fixed #1037165, bug fixed #812059.
Based on Percona Server 5.5.29-29.4 including all the bug fixes in it, Percona XtraDB Cluster 5.5.29-23.7.1 is now the current stable release. All of Percona‘s software is open-source and free.
We did our best to eliminate bugs and problems, but this is a software, so bugs are expected. If you encounter them, please report them to our bug tracking system.
Hi
source, deb and rpm but no binary release?
Hi Patrik,
Binary release is now available as well.
Hi Hrvoje Matijakovic,
We did the upgrade to 5.5.29 on a Debian server with the Percona apt repository configured but got some problems with the upgrade which I listed/detailled on the 3rd post of this google groups topic :
https://groups.google.com/forum/?fromgroups=#!topic/percona-discussion/bOEclT7K7o
Do you have any informations or already reported/known problems with this upgrade please ?
Moreover, do you have any clue of the cause of the errors we got please ?
Thanks by advance.
Regards,
Laurent
Hi Laurent,
Nobody reported any problems with this release yet.
I’ve reported this as https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1112363
One of our build engineers will check it out, can you please subscribe to the bug in case any additional information is required.
Thank you for reporting this,
Hrvoje
Hi Hrvoje,
Thanks for your quick reply and action.
In parallel, I had some reply from another Galera/Percona XtraDB user on codership google groups that had the same behavior :
https://groups.google.com/forum/?fromgroups=#!topic/codership-team/CgxIeofjJss
I will subscribe to the bug entry on launchpad.
Regards,
Laurent
Hello,
I believe that the bug of RPM rhel5 packages conflicting with mysql/mysql-server/mysql-libs is still persistent in some form, I’ll try finding the bug and re-opening it however let me put a snippet here from attempting to update from the previous version 5.5.28-23.7.370.rhel5, I am sure that if I attempted to revert those changes within the SRPM I would successfully update the RPM since the old version gets installed/updated so easily without problems.
[root@****]# ll
total 33816
drwxr-xr-x 2 root root 4096 Feb 3 23:05 .
drw——- 12 root root 4096 Feb 3 23:04 ..
-rw-r–r– 1 root root 9496400 Jan 30 18:44 Percona-XtraDB-Cluster-client-5.5.29-23.7.1.387.rhel5.x86_64.rpm
-rw-r–r– 1 root root 3665947 Jan 30 18:44 Percona-XtraDB-Cluster-devel-5.5.29-23.7.1.387.rhel5.x86_64.rpm
-rw-r–r– 1 root root 20427834 Jan 30 18:44 Percona-XtraDB-Cluster-server-5.5.29-23.7.1.387.rhel5.x86_64.rpm
-rw-r–r– 1 root root 1017261 Jan 30 18:44 Percona-XtraDB-Cluster-shared-5.5.29-23.7.1.387.rhel5.x86_64.rpm
[root@****]# yum localupdate *
Loaded plugins: fastestmirror
Setting up Local Package Process
Examining Percona-XtraDB-Cluster-client-5.5.29-23.7.1.387.rhel5.x86_64.rpm: 1:Percona-XtraDB-Cluster-client-5.5.29-23.7.1.387.rhel5.x86_64
Marking Percona-XtraDB-Cluster-client-5.5.29-23.7.1.387.rhel5.x86_64.rpm as an update to 1:Percona-XtraDB-Cluster-client-5.5.28-23.7.370.rhel5.x86_64
Loading mirror speeds from cached hostfile
* addons: mirrors.service.softlayer.com
* base: mirrors.service.softlayer.com
* epel: http://ftp.nluug.nl
* extras: mirrors.service.softlayer.com
* updates: mirrors.service.softlayer.com
addons | 1.9 kB 00:00
base | 1.1 kB 00:00
epel | 3.7 kB 00:00
extras | 2.1 kB 00:00
updates | 1.9 kB 00:00
Excluding Packages in global exclude list
Finished
Examining Percona-XtraDB-Cluster-devel-5.5.29-23.7.1.387.rhel5.x86_64.rpm: 1:Percona-XtraDB-Cluster-devel-5.5.29-23.7.1.387.rhel5.x86_64
Marking Percona-XtraDB-Cluster-devel-5.5.29-23.7.1.387.rhel5.x86_64.rpm as an update to 1:Percona-XtraDB-Cluster-devel-5.5.28-23.7.370.rhel5.x86_64
Examining Percona-XtraDB-Cluster-server-5.5.29-23.7.1.387.rhel5.x86_64.rpm: 1:Percona-XtraDB-Cluster-server-5.5.29-23.7.1.387.rhel5.x86_64
Marking Percona-XtraDB-Cluster-server-5.5.29-23.7.1.387.rhel5.x86_64.rpm as an update to 1:Percona-XtraDB-Cluster-server-5.5.28-23.7.370.rhel5.x86_64
Examining Percona-XtraDB-Cluster-shared-5.5.29-23.7.1.387.rhel5.x86_64.rpm: 1:Percona-XtraDB-Cluster-shared-5.5.29-23.7.1.387.rhel5.x86_64
Marking Percona-XtraDB-Cluster-shared-5.5.29-23.7.1.387.rhel5.x86_64.rpm as an update to 1:Percona-XtraDB-Cluster-shared-5.5.28-23.7.370.rhel5.x86_64
Resolving Dependencies
–> Running transaction check
—> Package Percona-XtraDB-Cluster-client.x86_64 1:5.5.29-23.7.1.387.rhel5 set to be updated
—> Package Percona-XtraDB-Cluster-devel.x86_64 1:5.5.29-23.7.1.387.rhel5 set to be updated
—> Package Percona-XtraDB-Cluster-server.x86_64 1:5.5.29-23.7.1.387.rhel5 set to be updated
—> Package Percona-XtraDB-Cluster-shared.x86_64 1:5.5.29-23.7.1.387.rhel5 set to be updated
–> Finished Dependency Resolution
Dependencies Resolved
==================================================================================================================================================================================================
Package Arch Version Repository Size
==================================================================================================================================================================================================
Updating:
Percona-XtraDB-Cluster-client x86_64 1:5.5.29-23.7.1.387.rhel5 /Percona-XtraDB-Cluster-client-5.5.29-23.7.1.387.rhel5.x86_64 32 M
Percona-XtraDB-Cluster-devel x86_64 1:5.5.29-23.7.1.387.rhel5 /Percona-XtraDB-Cluster-devel-5.5.29-23.7.1.387.rhel5.x86_64 8.4 M
Percona-XtraDB-Cluster-server x86_64 1:5.5.29-23.7.1.387.rhel5 /Percona-XtraDB-Cluster-server-5.5.29-23.7.1.387.rhel5.x86_64 65 M
Percona-XtraDB-Cluster-shared x86_64 1:5.5.29-23.7.1.387.rhel5 /Percona-XtraDB-Cluster-shared-5.5.29-23.7.1.387.rhel5.x86_64 3.4 M
Transaction Summary
==================================================================================================================================================================================================
Install 0 Package(s)
Upgrade 4 Package(s)
Total size: 109 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
mysql conflicts with Percona-XtraDB-Cluster-client-5.5.29-23.7.1.387.rhel5.x86_64
mysql-devel conflicts with Percona-XtraDB-Cluster-devel-5.5.29-23.7.1.387.rhel5.x86_64
mysql-libs conflicts with Percona-XtraDB-Cluster-shared-5.5.29-23.7.1.387.rhel5.x86_64
mysql-server conflicts with Percona-XtraDB-Cluster-server-5.5.29-23.7.1.387.rhel5.x86_64
Complete!
(1, [u’Please report this error in http://bugs.centos.org/set_project.php?project_id=16&ref=http://bugs.centos.org/bug_report_page.php?category=yum'])
Hi,
We hit a bug concerning this release and it seems this is 5.5.29 that introduced this bug as 5.5.28 is not concerned, I entered a bug entry on launchpad :
https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1117175
Could it be possible that it’s related to the above mentionned fix against FK bugs mentionned in the ChangeLog please ? :
– Percona XtraDB Cluster would crash when processing a delete for a table with foreign key constraint. Bug fixed #1078346 (Seppo Jaakola).
– In some cases non-uniform foreign key reference could cause a slave crash. Fixed by using primary key of the child table when appending exclusive key for cascading delete operation. Bug fixed #1089490 (Seppo Jaakola).
Regards,
Laurent
Well,
Following up the rhel5 RPM upgrade/install problem, it looks like the fix applied for the Foreign Key resulting in a new test-build available through https://www.percona.com/downloads/TESTING/Percona-XtraDB-Cluster/5.5.29-23.7.2/release-5.5.29/389/ where it includes a fix for the RPM upgrade/install bug as well, though its not mentioned anywhere nor there were a reply added to the bug report followup.
Regardless of all, thanks for fixing this issue as well.