Percona XtraDB Cluster 5.5.37-25.10 is now available_MySQL
Percona is glad to announce the release ofPercona XtraDB Cluster5.5.37-25.10 on May 8, 2014. Binaries are available from thedownloads areaor from oursoftware repositories.
Based onPercona Server 5.5.37-35.0including all the bug fixes in it, Galera Replicator 2.10 (including fixes in2.9and2.10milestones) and on wsrep API 25.10 (including fixes in 25.10),Percona XtraDB Cluster5.5.37-25.10is now the current stable release. All of Percona‘s software is open-source and free.
New Features:
- Percona XtraDB Clusternow supports stream compression/decompression with new xtrabackup-sstcompressor/decompressoroptions.
-
Garbdinit script and configuration files have been packaged forCentOSandDebian, in addition, inDebiangarbdis packaged separately inpercona-xtradb-cluster-garbd-2.xpackage. - New meta packages are now available in order to make thePercona XtraDB Clusterinstallationeasier.
- Debian/Ubuntudebug packages are now available for Galera and garbd.
- New SST options have been implemented:inno-backup-opts, inno-apply-opts, inno-move-optswhich pass options to backup, apply and move stages of
innobackupex. - Initial configurable timeout, of 100 seconds, to receive a first packet via SST has been implemented, so that if donor dies somewhere in between, joiner doesn’t hang. Timeout can be configured with thesst-initial-timeoutvariable.
- The joiner would wait and not fall back to choosing other potential donor nodes (not listed inwsrep_sst_donor) by their state. This happened even when comma was added at the end. This fixes it for that particular case.
- Support for Query Cache has been implemented.
- Percona XtraDB Cluster packages are now available for Ubuntu 14.04.
Bugs Fixed:
- To avoid disabling Parallel Apply in case of
SAVEPOINTorROLLBACK TO SAVEPOINTthewsrep_cert_deps_distancewas set to1.0at all times. Bug fixed#1277703. - First connection would hang after changing thewsrep_cluster_addressvariable. Bug fixed#1022250.
- When
gmcast.listen_addrvariable was set manually it did not allow node’s own address ingcommaddress list. Bug fixed#1099478. -
wsrep_sst_rsyncwould silently fail on joiner whenrsyncserver port was already taken. Bug fixed#1099783. - Server would segfault on
INSERT DELAYEDwithwsrep_replicate_myisamset todue to unchecked dereference ofNULLpointer. Bug fixed#1165958. - When
grastate.datfile was not getting zeroed appropriately it would lead to RBR error during the IST. Bug fixed#1180791. - Due to the
Provides:line inPercona XtraDB Cluster(which providesPercona-Server-server), the commandyum install Percona-Server-serverwould installPercona XtraDB Clusterinstead of the expectedPercona Server. Bug fixed#1201499. - Replication of partition tables without binlogging enabled failed, partition truncation didn’t work because of lack of TO isolation there. Bug fixed#1219605.
- Exception during group merge after partitioning event has been fixed. Bug fixed#1232747.
- Default value for
binlog_formatis nowROW. This is done so thatPercona XtraDB Clusteris not started with wrong defaults leading to non-deterministic outcomes like crash. Bug fixed#1243228. -
CREATE TABLE AS SELECTwas not replicated, if the select result set was empty. Bug fixed#1246921. -
INSERTwould return deadlock instead of duplicate key on secondary unique key collision. Bug fixed#1255147. - Joiner node would not initialize storage engines if
rsyncwas used for SST and the first view was non-primary. Bug fixed#1257341. - Table level lock conflict resolving was releasing the wrong lock. Bug fixed#1257678.
- Resolved the perl dependencies needed forPercona XtraDB Cluster5.5. Bug fixed#1258563.
- Obsolete dependencies have been removed fromPercona XtraDB Cluster. Bug fixed#1259256.
- GCache file allocation could fail if file size was a multiple of page size. Bug fixed#1259952.
- Percona XtraDB Clusterdidn’t validate the parameters ofwsrep_provider_optionswhen starting it up. Bug fixed#1260193.
- Runtime checks have been added for dynamic variables which are Galera incompatible. Bug fixed#1262188.
- Node would get stuck and required restart if DDL was performed after
FLUSH TABLES WITH READ LOCK. Bug fixed#1265656. - xtrabackup-v2is now used as default SST method inwsrep_sst_method. Bug fixed#1268837.
-
FLUSH TABLES WITH READ LOCKbehavior on the same connection was changed to conform toMySQLbehavior. Bug fixed#1269085. - Read-only detection has been added in
clustercheck, which can be helpful during major upgrades (this is used byxinetdforHAProxyetc.) Bug fixed#1269469. - Binary log directory is now being cleanup as part of the XtraBackup SST. Bug fixed#1273368.
- Deadlock would happen when
NULLunique key was inserted. Workaround has been implemented to supportNULLkeys, by using themd5sum of full row as key value. Bug fixed#1276424.
This release contains almost 100 fixed bugs, complete list of fixed bugs can be found in ourrelease notes.
Please see the5.5.37-25.10 releases notesfor complete details on all of the new features and bug fixes. Help us improve quality by reporting any bugs you encounter using ourbug tracking system. As always, thanks for your continued support of Percona!
Percona XtraDB ClusterErratacan be found in our documentation.
Hot AI Tools
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Undress AI Tool
Undress images for free
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Hot Topics
1392
52
When might a full table scan be faster than using an index in MySQL?
Apr 09, 2025 am 12:05 AM
Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.
Explain InnoDB Full-Text Search capabilities.
Apr 02, 2025 pm 06:09 PM
InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.
Can I install mysql on Windows 7
Apr 08, 2025 pm 03:21 PM
Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.
Difference between clustered index and non-clustered index (secondary index) in InnoDB.
Apr 02, 2025 pm 06:25 PM
The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.
MySQL: Simple Concepts for Easy Learning
Apr 10, 2025 am 09:29 AM
MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.
The relationship between mysql user and database
Apr 08, 2025 pm 07:15 PM
In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.
Can mysql and mariadb coexist
Apr 08, 2025 pm 02:27 PM
MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
Explain different types of MySQL indexes (B-Tree, Hash, Full-text, Spatial).
Apr 02, 2025 pm 07:05 PM
MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.
