It gives us great pleasure to announce that the 7.6 release of MySQL Cluster is now ready for prime time.
MySQL Cluster is the distributed database combining linear scalability and high availability. It provides in-memory real-time access with transactional consistency across partitioned and distributed datasets designed for mission critical applications.…
In the Replication QA team, we have been continuing to improve test coverage for Replication and Group Replication primarily to ensure that we support the newest and latest offerings of MySQL Server 8.0 such as Generated Columns, Set Persist, User Roles, and User Management DDLs that are now atomic.…
Overview
In MCM 1.4.6, the list backups command has been extended with a new –agent option for listing agent backups created with the backup agents command.
|
1 2 3 4 5 6 7 8 9 |
mcm> list backups --agent mysite; +------------+-------+---------+----------------------+---------+ | BackupId | Agent | Host | Timestamp | Comment | +------------+-------+---------+----------------------+---------+ | 1522914101 | 0 | tonfisk | 2018-04-05 07:41:41Z | | | 1522914105 | 0 | tonfisk | 2018-04-05 07:41:45Z | | | 1522914121 | 0 | tonfisk | 2018-04-05 07:42:01Z | | +------------+-------+---------+----------------------+---------+ 3 rows in set (0.00 sec) |
The output can be filtered with the –backupid option:
|
1 2 3 4 5 6 7 |
mcm> list backups --agent --backupid=1522914121 mysite; +------------+-------+---------+----------------------+---------+ | BackupId | Agent | Host | Timestamp | Comment | +------------+-------+---------+----------------------+---------+ | 1522914121 | 0 | tonfisk | 2018-04-05 07:42:01Z | | +------------+-------+---------+----------------------+---------+ 1 row in set (0.07 sec) |
The backupids for agent backups reflect the Unix Epoch times at which the backups were taken.…
MySQL 8.0 became Generally Available (GA) on April 19th, a great moment for us working on MySQL at Oracle. It is now a “fully grown adult” packed with new features, and improvements to existing features, as described here.
This blog post focuses on the impact of replication performance improvements that went into MySQL 8.0.…
MySQL 8.0.11 introduced a new performance schema table named log_status, which provides consistent information about MySQL server instance log positions from replication and transactional storage engines.
Used in conjunction with other MySQL 8.0 feature (the backup lock), this new feature will allow backup tools to take backup with minimal impact in DML throughput, but ensuring consistent snapshot with respect to GTIDs, replication, binary logs and transactional storage engine logs.…
MySQL 8.0.2 introduced a small yet powerful per transaction metadata information containing the transaction length in binary logs.
MySQL binary logs are being used for many other things than MySQL replication or backup/recovery: replicate to Hadoop; replicate to other databases, such as Oracle; capture data change (CDC) and extract-transform-load (ETL); record change notification for cache invalidation; change tracking for differential backups; etc.…
It is with extreme delight and a big smile on our face that we share the news that a new major MySQL release has been declared Generally Available (GA). The road to MySQL 8 was pretty eventful, sometimes painful and sometimes hard, always challenging, but nonetheless a great ride and an extremely rewarding journey for the engineers that have worked on it.…
Always having in mind providing the latest and the greatest features to our users, we decided to backport Hostname support in Group Replication Whitelist, starting in 5.7.21. Please check the developer blog in here and the official documentation here.
Download MySQL 5.7.21 GA release, and let us know your feedback or doubts through comments on this blog or MySQL bugs.…
Since January 2017, the MySQL Replication Team has been involved in processing many Community Contributions !
We are really happy to receive contributions (and not only in the replication team), but this also implies a lot of work from our engineers, as more than resolving a bug or developing a new feature, code contributions need to be analyzed, the code needs to be understood and validated.…
In order to improve observability and manageability of MySQL Group Replication (GR), we enhanced its instrumentation in MySQL 8.0.4. With these goals in mind, we have extended the usage of Performance Schema (P_S) from this plugin to the included Group Communication System (GCS) module as well as its submodule eXtended Communications (XCom) which are responsible for all communication involved in the dissemination of transactions to other MySQL instances.…
