Monthly Archives - June 2014

How to avoid even more of the common (but deadly) MySQL development mistakes

On July 16 I’ll be presenting my next webinar focusing on common mistakes committed by MySQL users.
How to Avoid Even More of the Common (but Deadly) MySQL Development Mistakes

“Why can’t I just save my data to a file?”
Using an SQL database seems so complex to get right, and for good reason. The variety of […]

Read more

Failover with the MySQL Utilities – Part 1: mysqlrpladmin

MySQL Utilities are a set of tools provided by Oracle to perform many kinds of administrative tasks. When GTID-replication is enabled, 2 tools can be used for slave promotion: mysqlrpladmin and mysqlfailover. We will review mysqlrpladmin (version 1.4.3) in this post.
Summary

mysqlrpladmin can perform manual failover/switchover when GTID-replication is enabled.
You need to have your servers […]

Read more

Why a Partitioned Collection Cannot Be Sharded

In TokuMX 1.5, we introduced partitioned collections for non-sharded clusters. That is, one can have a partitioned collection in a replica set, but one cannot shard a partitioned collection. In this post, I explain why.
As I mentioned here, partitioned collections are useful for time-series data where we would like to keep a rolling period […]

Read more

Percona Server with TokuDB (beta): Installation, configuration

My previous post was an introduction to the TokuDB storage engine and aimed at explaining the basics of its design and how it differentiates from InnoDB/XtraDB. This post is all about motivating you to give it a try and have a look for yourself. Percona Server is not officially supporting TokuDB as of today, though […]

Read more

TokuMX Compression & Performance Innovation Awards @ MongoDB World 2014

Today, at MongoDB World 2014 in New York City, we announced the winners of our inaugural TokuMX Compression & Performance Innovation Award. We selected two winners from amongst the nominees – Brightcove and Crowdtap. The announcement was made at the TokuMX Scale-up & Slim-down breakfast meet-up.
This morning’s meet-up featured special guests Mark Callaghan of […]

Read more

Why %util number from iostat is meaningless for MySQL capacity planning

Earlier this month I wrote about vmstat iowait cpu numbers and some of the comments I got were advertising the use of util% as reported by the iostat tool instead. I find this number even more useless for MySQL performance tuning and capacity planning.
Now let me start by saying this is a really tricky and deceptive number. Many […]

Read more

Sysbench Benchmarking of Tesora’s Database Virtualization Engine

Tesora, previously called Parelastic, asked Percona to do a sysbench benchmark evaluation of its Database Virtualization Engine on specific architectures on Amazon EC2.
The focus of Tesora is to provide a scalable Database As A Service platform for OpenStack. The Database Virtualization Engine (DVE) plays a part in this as it aims at allowing databases […]

Read more

Getting to know TokuDB for MySQL

During last April’s Percona Live MySQL Conference and Expo, TokuDB celebrated it’s first full-year as an open source storage engine. I still remember reading the official announcement and the expectations it created one year ago. The premises were very interesting as it had the potential of helping MySQL manage “big data” in a way InnoDB […]

Read more

TokuMX @ MongoDB World 2014

On Monday, some of the Boston-area Tokutek team will board New York bound trains to join our Union Square colleagues at MongoDB World 2014. We couldn’t be more excited.
You would be too. TokuMX, our high-performance distribution of MongoDB, just had its first birthday. The rapid acceptance by the MongoDB community has surpassed even our […]

Read more

How to setup Docker for Percona ClusterControl and add existing Percona XtraDB Cluster

In my previous post I showed you how to setup Percona XtraDB Cluster 5.6 on Docker. This time I will show you how to setup Percona ClusterControl and add the existing Percona XtraDB Cluster 5.6 that we’ve managed to setup from the previous post.
Let us note the following details about our existing containers:

172.17.0.2 dockerpxc1
172.17.0.3 […]

Read more