Overview

There are times when I need to restore a slave from a backup of a master or another slave, but too many times I have taken the typical approach of taking the backup on the source server and then copying it to the target server.  This takes a great deal of time, especially as your database grows in size.

These steps are going to detail how to use Netcat (nc) and Percona Xtrabackup (innobackupexec) to stream the backup from the source server to the target server, saving a great deal of time by copying the data only once to the desired location.  While the data is streaming to the target server, it’s being compressed and then uncompressed on the fly, reducing the amount of traffic going across the network by around 85% to 90% (typical backup compression ratios of MySQL Innodb I have witnessed are in this range).  I will also provide a simple script to complete these steps to give you a start at creating your …

In this blog post, we have multiple OLTP performance benchmarking scenarios using sysbench 1.0.14 on InnoDB and MyRocks. InnoDB and MyRocks (RocksDB with MySQL) are definitely not to supplement each other, They actually compliment well with respective advantages, Let me quickly explain how InnoDB and MyRocks can benefit you when used wisely, Again this blog post is not to show who (InnoDB or MyRocks) is better ? We regularly benchmark both of these storage engines before recommending to our customers on what is best suited for their database infrastructure operations ? so we would like to share our thoughts on this post.

How InnoDB and MyRocks are different ?

• MyRocks supports only READ-COMMITTED isolation level, There is no REPEATABLE-READ isolation level like InnoDB so no gap locking like InnoDB, We have written detailed blog on InnoDB transaction isolation levels …

Protective convenience
Recent versions of MySQL has an added security feature, the –login-path option. This feature puts your username and password in an encrypted file, and you refer clients to this file instead of typing plain text passwords on the console, or putting them in scripts.

…

From June 16th to 17th, the MySQL Team will be attending and speaking at the Hong Kong Open Source Conference 2018.

Unfortunately I won’t be present but some of my great colleagues will be speaking about MySQL.

If you are planning to attend HKOSCon2018, don’t miss their talks:

• Heading to the New Stage of MySQL 8.0 – Ivan Ma
• Crossing Relation and Document Database using …

If you attended my latest Troubleshooting MySQL Concurrency Issues with Load Testing Tools webinar you learned how I exploit benchmarking tools to replicate locking issues and crashes. But I told you nothing about proper use of these tools: for reliable benchmarks. I did not tell you that for a reason… I am just a Support Engineer and not a benchmarking expert.

And I have a dream. I want to invite world famous MySQL benchmarking experts for a Percona webinar and ask them for their secrets. I have a pretty long list of my own questions, but in order to make 1-hour webinar productive, we need to concentrate on just a few of the hottest ones. Therefore I need your help.

Please add your questions into the comments field of this blog post. Then we will choose the most important and/or most popular of …

Recently during my several talks and trips to meet the MySQL Community and MySQL InnoDB Cluster, I realized that some important message was missing. I got a lot of questions about which version of Router or Shell people should use. There is some confusion about which version to use, it seems that people thinks they should use MySQL Shell 1.0.x and MySQL Router 2.1.x with MySQL 5.7 and use the 8.0.x version having the same version as MySQL 8.0. This is wrong !

In fact, whatever the version of MySQL InnoDB Cluster you are using, you should ALWAYS use the latest version of Router and Shell. Currently it’s 8.0.11. So yes, even if you use MySQL 5.7.22, you MUST use MySQL Router 8.0.11 and …

This Wednesday, 6th June 2018, I will be presenting at OpenExpo Europe in Madrid: Experiences with testing dev MySQL versions and why it’s good for you.  It’s always good to test new releases of MySQL and this presentation talks about why.  If you are at the conference then please come along and say hello. Update 2018-06-07.  … Continue reading I will be presenting at OpenExpoEurope in Madrid on Wednesday

In this blog, I will provide answers to the Q & A for the Troubleshooting MySQL Concurrency Issues with Load Testing Tools webinar.

First, I want to thank everybody for attending my May 23, 2018, webinar on troubleshooting tools for MySQL. The recording and slides for the webinar are available here. Below is the list of your questions that I was unable to answer fully during the webinar.

Q: What do you recommend for benchmarking NDB cluster? Which should be used and how?

A: The issue with benchmarking NDB cluster is not the tool choice, but …

In a spirit of open source, and furthering our stated mission to be the unbiased champions of open source database software, we’re excited to introduce this community initiative. Our aim is to provide a platform for members of the open source database community to exchange ideas and knowledge, make suggestions and sound out ideas.

In some ways, you might view it as an all year-round, online celebration of what delegates enjoy about the Percona Live Open Source Database Conference. Something of a misnomer since Percona Live – as many readers will already know – is not just about Percona Software but embraces all open source database technology.

So it will be with this blog space.

Who will write for the Percona community blog?

If you already blog, then maybe you don’t want to be providing content for this blog too. Then again – if you post great …

MySQL Cluster 7.6 is GA!
If you’re eager to give the recently announced MySQL Cluster 7.6 GA a spin, I’ll walk you through a quick and simple way to get started using MySQL Cluster Manager 1.4.6.

Bootstrap and go!

1. Download and install MCM and MySQL Cluster
2. Bootstrap a cluster with MCM
   
   $ mcmd –bootstrap
3. Connect to the database, and have at it
   
   $ mysql -h 127.0.0.1 -P 3306 -u root

That simple.…