Now that MySQL 5.7 has become GA it’s a good time to highlight how much performance has improved in replication since the 5.6 era. This blog post will focus on the performance of the multi-threaded slave applier (MTS), and about it’s scalability in particular.…

MySQL 5.7.9 has a new feature, that simplifies queries that deal with JSON data and makes more human-readable: inlined JSON path expressions. Now you can do following:

mysql> CREATE TABLE employees (data JSON);
Query OK, 0 rows affected (0,01 sec)

mysql> INSERT INTO employees VALUES ('{"id": 1, "name": "Jane"}');
Query OK, 1 row affected (0,00 sec)

mysql> INSERT INTO employees VALUES ('{"id": 2, "name": "Joe"}');
Query OK, 1 row affected (0,00 sec)

mysql> SELECT * FROM employees WHERE data->'$.id'= 2;

+--------------------------+
| data                     |
+--------------------------+
| {"id": 2, "name": "Joe"} |
+--------------------------+
1 row in set (0,01 sec)

Let’s take a closer look at the expression in the WHERE clause.…

MySQL 5.7 has been recently declared Generally Available and in it there is a set of new replication features. Over the last 6 years MySQL replication has evolved at a tremendous pace. MySQL 5.6 brought us a lot of new replication features, many that were ground breaking and yes, sometimes controversial.…

Many of our users speak highly of our product ClusterControl, especially how easy it is to install the software package. Installing new software is one thing, but using it properly is another.

We all are impatient to test new software and would rather like to toy around in a new exciting application than to read documentation up front. That is a bit unfortunate as you may miss the most important features or find out the way of doing things yourself instead of reading how to do things the easy way.

This new blog series will cover all the basic operations of ClusterControl for MySQL, MongoDB & PostgreSQL with examples explaining how to do this, how to make most of your setup and provides a deep dive per subject to save you time. 

These are the topics we'll cover in this series:

• Deploying the first clusters
• Adding your existing infrastructure
• Performance and health monitoring …

The MySQL Fabric team is pleased to announce that a new version is now available on Labs. This labs release includes our latest developments to give you a taste of what we have been working on. In particular, it includes the following new features and improvements:

• Multi-node Fabric support is now available! This means that multiple fabric nodes can be started and any node can be contacted to perform operations. This allows Fabric itself to be fault-tolerant (no single point of failure) and distribute request across multiple Fabric nodes. For more information, see: Increasing MySQL Fabric Resilience to Failures: Meet the Multi-Node Fabric 
• Improved security password management, allowing password to not be passed in plain text in the command line or configuration files. …

I had an interesting task of collecting and displaying some runtime metrics during the benchmark. Since data was clearly divided between OS and processes, I opted for separate background jobs in which case no task will stall the other. However, this means I had to establish communication between main script code and jobs which is tricky in Powershell (see this bug for example). Immediately, I thought of using named pipes or files (as I do have small, ever changing set of data). Further investigation revealed 4 ways of accomplishing this:

1. Using files

• pros:
  • Tried and tested; works everywhere.
  • Intuitive.
  • File management routines are mature.
• …

An application always needs support of concurrent connections to mysql servers and always requires high available system for a loss less data environment.

The MySQL Router is a new building block for high availability solutions. MySQL Router simplifies development of high availability applications by intelligently routing queries to MySQL Servers for increased performance, robustness, and uptime. MySQL Router definitely helps in supporting HA and concurrent connections to servers without any change in the application level coding irrespective of the servers in a simple topology or in a fabric distributed server.

In a practical application environment, the data is fetched from the read-only servers where data is written to read-write servers. So Router is pre-defined to support similar server setup. Also it is required connect to the available/next available server when there is failover and Provide proper logs to the …

The MySQL Router is a new building block for high availability solutions. MySQL Router simplifies development of high availability applications by intelligently routing queries to MySQL Servers for increased performance, robustness, and uptime.

MySQL Router also connects seamlessly with MySQL Fabric permitting Fabric to store and manage the high availability groups for routing, making it simpler to manage groups of MySQL Servers for redundancy and
continued operation.Also You do not need specific fabric aware connectors to do so. You can use generic MySQL Connectors for this purpose.

Please refer to http://dev.mysql.com/doc/mysql-router/en/mysql-router-installation.html to install MySQL Router.
Create a fabric setup using https://dev.mysql.com/doc/mysql-utilities/1.4/en/fabric-setup.html

How to integrate Router with MySQL Fabric:
you can have one MySQL Fabric state-store …

The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.5. This is a maintenance release for 1.3.x. It can be used for production environments.

MySQL for Excel is an application add-in enabling data analysts to very easily access and manipulate MySQL data within Microsoft Excel. It enables you to directly work with a MySQL database from within Microsoft Excel so you can easily do tasks such as:

• Importing MySQL data into Excel
• Exporting Excel data directly into MySQL to a new or existing table
• Editing MySQL data directly within Excel

MySQL for Excel is installed using the MySQL Installer for …

It was exactly 2 years now since we reached 500K QPS with MySQL 5.7 -- it was a great milestone, and the highest ever result seen on MySQL with true SQL queries ;-)) And this was on 32cores-HT machine.. (the linked article contains the whole long story how we arrived to 250K QPS first, then 275K, 350K, 440K, and finally 500K QPS) -- the main improvement here is coming from greatly redesigned transactions and transaction list management in MySQL 5.7.

However, when the 40cores-HT server arrived to MySQL LAB we were not yet ready to show more than 500K QPS -- there were still some other contentions on external to InnoDB level.. Once these all were fixed, we finally reached 645K QPS on 40cores-HT server and pushed the limit more far yet ;-) -- this is what we were able to announce a year ago, …