MySQL has provided support for proxy users since version 5.5, but the roles-like capabilities offered have been largely unnoticed until recently.  Part of that has been due to limitations on which types of accounts could leverage proxy user capabilities.  This changes with the release of MySQL Server 5.7.7 (Release Candidate), which includes support for proxy user mapping for the standard mysql_native_password and sha256_password authentication plugins.  This post will introduce the new functionality and explain how to leverage it to emulate certain features …

The MySQL Development team is very happy to announce that MySQL 5.7.7, the first 5.7 Release Candidate (RC1), is now available for download at dev.mysql.com (use the “Development Releases” tab). You can find the full list of changes and bug fixes in the 5.7.7 release notes. Here are some highlights. Enjoy!

SYS Schema

Include SYS Schema in MySQL 5.7 (WL#8159) — This work by Mark Leith integrates the SYS Schema (formerly ps_helper) within the MySQL Server by default. The MySQL SYS schema project has …

A week from today I am speaking at Percona Live: MySQL Conference and Expo 2015.

Here is my talk:

• Assembling the perfect MySQL toolbox

My talk is for anyone who wants to make their life easier using MySQL tools. Rather than doing a deep dive on one or two tools, I will describe the methodology we've used at Flite to successfully integrate many different MySQL tools into our day-to-day workflow. The talk will take place Wednesday, April 15 at 3:30 PM in Ballroom E.

I most recently gave this talk at the San Francisco MySQL Meetup in February. If you are interested in my talk but won't be at Percona Live, you can find the video …

Dealing with the failure of a MySQL master is not simple.  The most common solution is to promote a slave as the new master but in an environment where you have many slaves, the asynchronous implementation of replication gets in your way.  The problem is that each slave might be in a different state:

some could be very close to the dead master, some could be missing the latest transactions, and

Last week, we introduced VividCortex support for Redis. One of the reasons we expanded our product capabilities is because of our own use of Redis. According to Baron, “We rely on Redis to help analyze the massive amounts of time-series data we receive from agents running on customer systems.” Let’s go a little deeper…

VividCortex keeps tables with all the known metrics and queries for many hosts measured at 1-second granularity. We use Redis to avoid repeating the “insert on duplicate update” into the metric/query tables. We are able to do this by keeping hourly buckets of seen queries and metrics. When a batch of metrics/queries arrive, before insert/updating them in the mysql tables, we check that we haven’t …

Don't miss these MySQL clustering and replication keynotes and sessions next week:

Keynote: What has the cloud done lately for my data? (Robert Hodges, VMware)  Moving Workloads Effectively to Hybrid Cloud Deployments (MC Brown, VMware)  Tutorial: Advanced MySQL replication features roundup (Giuseppe Maxia, VMware) Pivot tables: Analytics in pure SQL (Giuseppe Maxia, VMware) The perils of

Last time we set up a High Availability server farm with MySQL Fabric. Now it is time to set up sharding. I will be using the good old World database and sharding the City table on the ID field. There are 4,079 cities in this table and they will be split in two. So one shard, that we will call CityLow will have the records 2,000 and below and the other records at 2,001 and above will be called CityHigh. We also need a global group for setting up sharding that will be called CityGlobal.

Sadly, the first step is to remove the previous setup with mysqlfabric manage teardown. This will remove the fabric database from the Fabric controller. Fabric itself has to be stopped with mysqlfabric manage stop. The command mysqlfabric manage setup will set up a fresh, clean fabric database. And …

(この記事は InnoDB Full-Text: MeCab Parser を Yoshiaki Yamasaki が翻訳したものです)

このブログ記事で紹介した一般的なCJK(中国語、日本語、韓国語)のサポートに加えて、私達はMeCabパーサーも追加しました。MeCabは日本語の形態素解析エンジンで、私達は今 …

Tue, 2015-04-07 11:41guillaumelefranc

In the first blog of these series, we've done a rapid walkthrough on how to use Ansible and Vagrant to start a master/slave pair. In this second post, we will delve into the inner workings of Ansible, explaining how to set up server inventories, automate MariaDB deployments, use configuration templates and much more.

Setting up an Ansible inventory

Once Ansible is setup with your usual package manager, the first task should be to create passwordless SSH keys and to setup the servers you want to manage for passwordless access. Setting up SSH keys is extensively described on the internet so I won't get into any details in this post.

The second task is to create a server inventory. This is as …

Due to its synchronous nature, Galera performance can be limited by the slowest node in the cluster. So running heavy reporting queries or making frequent backups on one node, or putting a node across a slow WAN link to a remote data center might indirectly affect cluster performance. Combining Galera and asynchronous MySQL replication in the same setup, aka Hybrid Replication, can help. A slave is loosely coupled to the cluster, and will be able to handle a heavy load without affecting the performance of the cluster. The slave can also be a live copy of the Galera cluster for disaster recovery purposes.

We had explained the different steps to set this up in a previous post. With ClusterControl 1.2.9 …