Dear community, maybe you have already tested, there are new added features in MySQL 5.7. See previous post -> About 5.7.7-rc BUGs

“General Tablespace” feature -> From now you can place tables to separate tablespaces. Prior, on our hands there were only “System TableSpace” and “InnoDB file per table” options. Today’s topic is altering table to use this “General Tablespace”.

Our sample table structure:

mysql> show create table t1;

    | Table | Create Table 
    | t1    | CREATE TABLE `t1` (
      `id` int(11) DEFAULT NULL,
      `c1` varchar(85) DEFAULT NULL
    ) /*!50100 TABLESPACE innodb_file_per_table */ ENGINE=InnoDB DEFAULT CHARSET=utf8 

Note that there is a comment about tablespace of our table -> /*!50100 TABLESPACE …

Welcome to MySQL QA Episode 8: Reducing Testcases for Engineers: tuning reducer.sh

1. Advanced configurable variables & their default/vanilla reducer.sh settings
   1. FORCE_SKIPV
   2. FORCE_SPORADIC
   3. TIMEOUT_COMMAND & TIMEOUT_CHECK
   4. MULTI_THREADS
   5. MULTI_THREADS_INCREASE
   6. QUERYTIMEOUT
   7. STAGE1_LINES
   8. SKIPSTAGE
   9. FORCE_KILL
2. Some examples
   1. FORCE_SKIPV/FORCE_SPORADIC
   2. TIMEOUT_COMMAND/TIMEOUT_CHECK

Full-screen viewing @ 720p resolution recommended.

The post MySQL QA Episode 8: Reducing Testcases for Engineers: tuning reducer.sh …

[…] ← innodb_fast_checksum=1 and upgrading to MySQL 5.6 […]

Summary: My checklist for performing an in-place MySQL upgrade to 5.6. Details: In my previous post, I discussed the problem I had when doing an in-place MySQL upgrade from 5.5 to 5.6 when the database had been running with innodb_fast_checksum=1. … Continue reading →

I recently worked with a customer who had a weird issue: when their MySQL server was started (Percona Server 5.5), if they try to run service mysql start a second time, the init script was not able to detect that an instance was already running. As a result, it tried to start a second instance with the same settings as the first one. Of course this fails and this creates a mess. What was the issue? A missing rule in SELinux. At least it looks like

Summary

If SELinux is set to enforcing and if you are using Percona Server on CentOS/RHEL 6 (other versions could be affected), service mysql start doesn’t work properly and a fix is simple to run:

# grep mysqld_safe /var/log/audit/audit.log | audit2allow -M mysqld_safe
# semodule -i mysqld_safe.pp
# service mysql restart

Other options are:

• Set SELinux to permissive
• Use the CentOS/RHEL standard MySQL init script …

Morgan and I started an initiative a while back to improve the “out of the box” configuration and behavior defaults for MySQL. Working closely with the Community, we were able to come up with a good list of improvements. This work really began to bear fruit starting with the MySQL 5.7.7 release.…

My latest post is online on the Booking.com blog: Evaluating MySQL Parallel Replication Part 3: Benchmarks in Production.  In this post, I present benchmark results on MariaDB 10.0 parallel replication on four Booking.com production workloads.

This post is also the opportunity to promote my two talks at Percona Live Europe, taking place in Amsterdam from September 21 to 23:

Binlog Servers at

#DBHangOps 07/23/15 -- Information Security, Database, and you!

Hello everybody!

Join in #DBHangOps this Thursday, July, 23, 2015 at 11:00am pacific (19:00 GMT), to participate in the discussion about:

• What does security mean for you?

  • What tools do you use to improve security?
  • What are good security settings for MySQL?

• What does Compliance mean for you?

  • Any useful tools?
  • What are good compliance settings for MySQL?

• Resolving production issues in a secure and compliant way

  • Do you have to change some ways your defenses and tools work for security/compliance?
  • How do you empower developers to debug production issues in a compliant and secure way? …

I’ve been invited to speak at a joint meeting of the Austin MySQL meetup and the Austin Data Geeks meetup on Monday, July 27, 2015. This is a real treat for me. I have not spent much time in this area but whenever I have I’ve loved it. And the community is large and highly engaged at lots of levels. Here’s the summary of the event:

… your database’s performance is a lot less important to your business than the way you structure your engineering team. The interesting thing is that a lot of the most serious team, communication, and process bottlenecks in your business (the ones that make you miss ship deadlines, crash the site, and lose your best team members after repeated all-nighters) are actually driven by database issues, but not the way you think they are. …

Continuing from our April 2015 release of the VMware Continuent 4.0 products is a new 4.0.1 release that provides important fixes to both the replication and MySQL clustering.For full details, read the full release notes, available at the links below, but the highlights are as follows: VMware Continuent for Replication and Data Warehousing

Expanded support for EBS Snapshots to enable MySQL table