Today SkySQL is changing its name to MariaDB Corporation.
This is something that I had both anticipated and I think it's a
great step for MariaDB.
I wanted here to to share my thoughts on how this change affects
the MariaDB community.
The short version: As the MariaDB Corporation is the main driving
force behind the development of the MariaDB server and the
biggest support provider for it, it makes sense to give it a name
that clearly communicates this fact. The name change
doesn't of course stop the company to continue it's excellent
support for MySQL.
For MariaDB users and customers, the name change should not
affect them in any way, except that it will make it easier for
them to find more information about MariaDB as there is fewer
names involved.
For the …
MySQL Fabric Support
MySQL Fabric servers can now be added to the Workbench home screen. When clicked, these connections will dynamically query the Fabric server and individual connections for all the managed MySQL servers will be created. You can then connect to each instance as usual.
Metadata Lock Browser
MySQL uses metadata locking to manage access to objects (tables, triggers, and so forth). Sometimes that can be puzzling, as your query may block waiting on an object being manipulated by another connection from maybe another user. The Client Connections list was updated to take advantage of the metadata lock information provided in the performance_schema starting in MySQL 5.7.3, to show …
[Read more]We have received a lot of requests from our user community regarding the ability to truncate UNDO tablespaces (‘truncate’ here means that the size of the tablespace is reset back to what it was when it was first created). We are happy to say that we’ve now been able to implement this anticipated feature.
Introduction
The InnoDB UNDO tablespace(s) host rollback segments that hold rollback information related to database changes. This information is used to rollback a transaction and to retrieve the previous version of a record that has been updated or deleted for multi-version concurrency control (MVCC). Once a transaction is committed, InnoDB will discard the related UNDO log records. UNDO log records for updates or deletes will be kept around as long as there exists an open transaction that may access older versions of the records. When all such open transactions are committed then the associated UNDO log records can …
[Read more]The multi master plugin for MySQL is here. MySQL Group Replication provides virtually synchronous updates on any node in a group of MySQL servers, with conflict handling and automatic group membership management and failure detection.
For a better understanding on how things work, we go under the hood in this post and will analyse the transaction life cycle on multi master and which components does it interact with. But before that we need to understand first what a group is.
Group Communication Toolkit
The multi master plugin is powered by a group communication toolkit. This is what decides which servers belong to the group, performs failure detection and orders server messages. Being the ordered messaging the magic thing that allows the data to be consistent across all nodes. You can check the details of the group communication toolkit at …
[Read more]More MySQL releases than ever before. Check out the following that we just released:
– MySQL Connector Java 5.1.33 GA
– MySQL Fabric & MySQL Utilities 1.5.2 GA
– MySQL Connector Python 2.0.1 GA
– MySQL Fabric and Utilities 1.6.0 Alpha
– MySQL Connector C (Labs)
– MySQL Connector Python (Labs)
– MySQL Group Replication (Labs)
– MySQL HTTP Plugin (Labs)
Download from http://dev.mysql.com/downloads/ and http://dev.mysql.com/downloads/
Percona is pleased to announce the availability of Percona Toolkit 2.2.11. Released on Sept. 25, Percona Toolkit is a collection of advanced command-line tools to perform a variety of MySQL server and system tasks that are too difficult or complex for DBAs to perform manually. Percona Toolkit, like all Percona software, is free and open source.
This release contains bug fixes for pt-query-digest, pt-mysql-summary, pt-stalk, as well as other tools and is the current GA (Generally Available) stable release in the 2.2 series. Downloads are available here and from the …
[Read more]The multi master plugin for MySQL is here “MySQL Group Replication“. It is a virtual synchronous solution for MySQL with conflict detection. It also supports automatic group membership management, failure detection and automatic distributed recovery.
With the introduction of this new feature there was a need to perform some good amount of testing as it involves complex functionalities like :
- Servers execute local transactions and broadcasts the update to the group.
- All servers in the group, even the sender, receive same transaction in the same order and check for conflicts.
- All servers, independently, decide to commit the transaction – no conflicts.
- A new node can join an existing group, so in this case we need distributed recovery to bring it at par with the other servers.
So a great deal of effort has been spent on testing these …
[Read more]Multi-master update everywhere solution for MySQL is here. MySQL Group Replication ensures virtual synchronous updates on any node in a group of MySQL servers, with conflict handling and failure detection. Distributed recovery is also in the package to ease the process of adding new nodes.
Starting with MySQL 5.7.2 there has been a constant effort from the replication team to provide more fields to monitor the replication performance in the performance schema tables. This post gives a brief overview of the Performance Schema tables that have been introduced for MySQL Group Replication.
TABLES INTRODUCED
There are two new tables introduced as a part of the MySQL Group Replication monitoring.
- performance_schema.replication_node_status
- performance_schema.replication_connection_nodes
Lets go through each table in detail :
REPLICATION NODE STATUS
…[Read more]With the introduction of Global Transaction Identifiers(GTID) in MySQL from mysql-5.6 GA a whole lot of different functionality have been developed around it so that GTID could be used in a much simpler and efficient way.
One of the interesting functionality with GTID in use is the
function to sync a slave with its
master server using the WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS. This
is used to do a timed or an indefinite wait till the servers
in contention are in sync with respect to the GTID executed set.
This function is used to address specific use cases in which transactions are applied using SQL/worker thread. In order to give more flexibility to the user a new function of syncing the servers with GTID has been introduced in mysql-5.7.5 called WAIT_FOR_EXECUTED_GTID_SET.
Limitations of WAIT_UNTIL_SQL_THREAD_AFTER_GITDS
The already existing WAIT_UNTIL_SQL_THREAD_AFTER_GITDS functions …
[Read more]On MySQL-5.7.2, we released a new type of multi-threaded slave (MTS). It is called logical clock based MTS. Because it can parallel apply transactions in the same schema, it has the potential to improve slave throughput on almost any application, regardless of the schema layout. After it was released, we continued to work on the framework to improve it further. Therefore, 5.7.5 includes a few enhancements, in addition to those released as part of previous DMRs. This blog post introduces one of the new features in the latest DMR.
slave_preserve_commit_order
It is a system global variable and can be set dynamically.
- SET GLOBAL slave_perserve_commit_order = {ON|OFF};
Enabling this variable ensures that the order which transactions were committed on the master is preserved on the slave. The replication threads must be stopped before enabling this variable and this variable only affects logical clock based …
[Read more]