Welcome to this week’s Planets9s, covering all the latest resources and technologies we create around automation and management of open source database infrastructures.

Some time ago, I published the article “AWS Aurora Benchmarking - Blast or Splash?”. In which I was analyzing the behavior of different solutions using synchronous replication in AWS environment.

After I published it, I received a lot of comments and feedback, from the community and from Amazon engineers.

Given that I had decide to perform another round of tests, keeping into account the comments received and the suggestions.

I had presented some of the results during the Percona conference in Santa Clara last April 2016. The following is the transposition into an article of that presentation with more details.

{autotoc enabled=yes}

Why new test?

Very good question, with an easy answer. …

In this blog, we’ll discuss how to find the MySQL 5.7 root password.

While new MySQL software security features are always welcome, they can impact use and performance. Now by default, MySQL 5.7 creates a password for the root user (among other changes) so the installation itself can be considered secure. It’s a necessary change, but it has confused some customers and users. I see a lot of people on social networks (like Twitter) asking about this change.

Where is my root password?

The answer depends on the way you have installed MySQL 5.7 or Percona Server 5.7. I am going to show where to find the password depending on the installation method and the distribution used. For all these examples, I assume this is a new installation and you are using the default my.cnf.

Centos/Redhat – …

Please join Alexander Rubin, Percona Principal Consultant, for his webinar MongoDB administration for MySQL DBA on Thursday, May 19 at 10 am PDT (UTC-7).

If you are a MySQL DBA and want to learn MongoDB quickly – this webinar is for you. MySQL and MongoDB share similar concepts so it will not be hard to get up to speed with MongoDB.

In this talk I will explain the following MongoDB administration concepts:

• Day to day operations for MongoDB
• Storage engines and differences with MySQL storage engines
• Databases, collections and documents
• Replication in MongoDB and the difference with MySQL replication
• Sharding in MongoDB
…

In this post, we’ll look at the results from some MySQL 5.7 read-write benchmarks.

In my past blogs I’ve posted benchmarks on MySQL 5.5 / 5.6 / 5.7 in OLTP read-only workloads. For example:

• MySQL 5.7 sysbench OLTP read-only results: is MySQL 5.7 really faster?
• MySQL 5.7 primary key lookup results: is it really faster?
• ProxySQL versus MaxScale for OLTP RO workloads

Now, it is time to test some read-write transactional workloads. I will again use sysbench, and my scripts and …

A few weeks ago my friend Frank de Jonge told me he managed to improve an import into a MySQL server down from more than 10 hours to 16 minutes. According to him it had to do with several field types (too long fields to really small data), the amount of indexes, and constraints on the tables. We were talking about 1 million records here. He wondered if it was possible to make it even faster.

The basics

Turns out there are many ways of importing data into a database, it all depends where are you getting the data from and where you want to put it. Let me give you a bit more context: you may want to get data from a legacy application that exports into CSV to your database server or even data from different servers.

If you are pulling data from a MySQL table into another MySQL table (lets assume they are into different servers) you might as well use …

The Severalnines team is pleased to announce the release of ClusterControl 1.3.

This release contains key new features, such as Key Management for MySQL, MariaDB, Percona Server and PostgreSQL, improved security, additional Operational Reports, along with performance improvements and bug fixes.

Join us next week on Tuesday, May 24th, for a live demo!

Sign up for the webinar

Highlights

• New for MySQL, MariaDB, Percona Server & PostgreSQL
  • Key Management
  • Additional Operational Reports
  • Improved Security
  • Create/Mirror Repository
• New for MySQL
  • Deploy Production Setup of NDB/MySQL Cluster
• New for MongoDB
  • Deploy Percona for MongoDB ReplicaSet Node …

ConFoo Vancouver: December 5th-7th 2016

We are happy to open the call for papers of ConFoo Vancouver 2016! If you are interested in speaking about web development and related topics, please submit until June 6th. We will cover travel and hotel for the speakers who require it if you want to know  the quality of a great check stub maker.

ConFoo Vancouver will be held on December 5-7, 2016. For those who are familiar with ConFoo Montreal, that conference will still be running annually in addition to Vancouver. Visit our site to learn more about the event and …

In this blog post, we’ll discuss the possible reasons for MySQL “Got an error reading communication packet” errors, and how to address them.

In Percona’s managed services, we often receive customer questions on communication failure errors – where customers are faced with intermittent “Got an error reading communication packets” messages. I thought this topic deserved blog post so we can discuss possible reasons for this error, and how to remedy this problem. I hope this will help readers on how to investigate and resolve this problem.

First of all, whenever a communication error occurs it increments the status counter for either Aborted_clients or …

Replication between Tungsten clusters

The process I will describe in this post will allow you to configure replication between Tungsten clusters. The most common use case I have seen for this is a dedicated ETL cluster.

The setup will look like this:

So we will have a composite datasource (compositeprod) composed of east and west clusters, and two ETL clusters, one on each side.

The described setup allows failover or switchover within a single datacenter (e.g. db1.east -> db2.east) or to the Disaster Recovery Site, (e.g. db1.east -> db1.west) for the core cluster.

At the time of this article’s publication it is not possible to replicate between two composite clusters, so each ETL cluster needs to be standalone. This feature is expected for Tungsten 5.0 release.

We will install a standalone replicator on the ETL hosts to bring data in …