Tag: MySQL 5.7

Feed: Planet MySQL; Author: Frederic Descamps; The MySQL Ecosystem has been using InnoDB as the default transactional engine for many years now. If you are one of the few still using MyISAM, it is time you also converted and benefited from InnoDB. If you plan to upgrade to MySQL 8.0, you have several options to deal with those MyISAM tables. Please note that you should not use MyISAM tables. MyISAM is not ACID compliant and can lead to data loss. Also MyISAM only supports full table lock and no row locking. As you may recall, in 5.7, MyISAM has MYD, MYI, ... Read More

Feed: Planet MySQL; Author: Codership; Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 5.7 and 8.0, consisting of MySQL-wsrep 5.7.34 (release notes, download) and MySQL-wsrep 8.0.25 (release notes, download) with Galera replication library 3.34 (release notes, download) implementing wsrep API version 25 and Galera replication library 4.9 (release notes, download) implementing wsrep API version 26. This release incorporates all changes to MySQL 5.7.34 and 8.0.25 respectively, adding a synchronous option for your MySQL High Availability solutions. We skipped releasing MySQL 8.0.24 because upstream released 8.0.25 fairly quickly with some bug ... Read More

Feed: Planet MySQL; Author: Codership; Codership is pleased to announce a new Generally Available (GA) release of the multi-master Galera Cluster for MySQL 5.6, 5.7 and 8.0, consisting of MySQL-wsrep 5.6.51 (release notes, download), 5.7.33 (release notes, download) and 8.0.23 (release notes, download) with Galera replication library 3.33 (release notes, download) implementing wsrep API version 25, and Galera replication library 4.8 (release notes, download) implementing wsrep API version 26 for 8.0. This release incorporates all changes to MySQL 5.6.51, 5.7.33 and 8.0.23 respectively, adding a synchronous option for your MySQL High Availability solutions. Throughout the entire packages, for the binary ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; As database footprints continue to explode, many companies are looking for ways to deal with such rapid growth.  One approach is to refactor traditional relational databases to fit into a NoSQL engine, where horizontal scalability is easier.  However, in many cases, this is in no way a trivial undertaking. Another approach that has been gaining interest is the use of MyRocks as an alternative storage engine to the traditional InnoDB.  While not for everyone, in certain use cases it could be a potential solution.  As with so many things open source, the next ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; Nobody likes change, especially when that change may be challenging.  When faced with a technical challenge, I try to remember this comment from Theodore Roosevelt: “Nothing in the world is worth having or worth doing unless it means effort, pain, difficulty.”  While this is a bit of an exaggeration, in this case, the main concept is still valid.  We shouldn’t shy away from an upgrade path because it may be difficult. MySQL 8.0 is maturing and stabilizing.  There are new features (too many to list here) and performance improvements.  More and more organizations ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; Transportable tablespaces were introduced in MySQL 5.6. Using this feature, we can directly copy a tablespace to another server and populate the table with data. This is a very useful feature for large tables. The transportable tablespace mechanism is faster than any other method for exporting and importing tables because the files containing the data just need to be copied to the target location using traditional Linux commands (cp, scp, rsync). Our post MySQL 5.6 Transportable Tablespaces best practices covers the best practices about transportable tablespaces. The feature also supports encrypted tablespaces, and ... Read More

Feed: Recent Announcements. Major version database upgrades can be challenging in self-managed environments. Managing backups, monitoring the upgrade process, and restoring from backup manually in the case of issues can result in unanticipated downtime for self-managed databases. For Amazon RDS for MySQL customers upgrading from MySQL 5.7 to MySQL 8.0, Amazon RDS introduced prechecks that identify potential issues before the upgrade begins, including both prechecks from MySQL and prechecks developed by the Amazon RDS team. Rollback protection extends the reliability of major version upgrades for RDS for MySQL instances beyond prechecks, and automatically reverts instances to a running state on ... Read More

Feed: Planet MySQL; Author: Percona Community; Wayne Leutwyler  | February 24, 2021 |  Posted In: Advanced Level, MySQL The ProblemHELP, HELP! My Percona XtraDB Cluster version: 5.7.31-31. Single Node is stuck in a joined state.I recently had the privilege to help a client with a fascinating issue.NODE-B dropped out of the 3 node PXC cluster. It looked to be DISK IO that caused NODE-B to fall far behind and eventually be removed from the cluster. A restart of NODE-B allowed itto rejoin the cluster. NODE-B looked to have been down for about 4 hours. Once NODE-B was back as part of the ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; MySQL 5.6.51 is the last release of the MySQL 5.6 series. Oracle will no longer provide updates or security fixes for this version. Following Percona’s Release Lifecycle policies, the Percona Server for MySQL 5.6 series has reached End of Life (EOL) as well, and we will no longer provide public builds for bugs and security fixes. We recommend that you upgrade to MySQL 5.7 or Percona Server for MySQL 5.7, or for the latest features, MySQL 8.0 or Percona Server for MySQL 8.0. Suppose you have not upgraded because you have off-the-shelf applications ... Read More

Feed: Planet MySQL; Author: MyDBOPS; From MySQL 5.7, we had a Multi-threaded Slave (MTS) Applier mechanism called LOGICAL_CLOCK to overcome the problems of parallel replication within a database. To further improve the parallelisation mechanism, from MySQL 8 (5.7.22) we have write-set replication, so before going further , lets look at the difference between Logical clock (LC) and Writeset. LOGICAL_CLOCK Transactions that are part of the same binary log group commit on a master are applied in parallel on a slave. The dependencies between transactions are tracked based on their timestamps to provide additional parallelisation where possible. WRITESET Write-set is a mechanism ... Read More