The MySQL Utilities Team is pleased to announce a new beta release of MySQL Utilities. This release includes a number of improvements for usability, stability, and a few enhancements. A complete list of all improvements can be found in our release notes.

New Enhancements!
This release represents a stable release of the product. Along with several defect patches, we also include the following enhancements.

Improved support for MySQL 5.7
Improved functionality of --exclude option with SQL wildcards
Improved packaging in RPM and Windows distributions
Improved accuracy of calculated disk usage for mysqldiskusage
...and a host of minor improvements for quality and robustness


How Can I Download MySQL Utilities?
You can download MySQL Utilities 1.6.3 Beta from the …

In this blog post, we’ll discuss some of the basics regarding Docker MySQL replication. Docker has gained widespread popularity in recent years as a lightweight alternative to virtualization. It is ideal for building virtual development and testing environments. The solution is flexible and seamlessly integrates with popular CI tools.

This post walks through the setup of MySQL replication with Docker using Percona Server 5.6 images. To keep things simple we’ll configure a pair of instances and override only the most important variables for replication. You can add whatever other variables you want to override in the configuration files for each instance.

Note: the configuration described here is suitable for development or testing. We’ve also used the …

This blog post discusses Orchestrator: MySQL Replication Topology Manager.

What is Orchestrator?

Orchestrator is a replication topology manager for MySQL.

It has many great features:

• The topology and status of the replication tree is automatically detected and monitored
• Either a GUI, CLI or API can be used to check the status and perform operations
• Supports automatic failover of the master, and the replication tree can be fixed when servers in the tree fail – either manually or automatically
• It is not dependent on any specific version or flavor of MySQL (MySQL, Percona Server, MariaDB or even MaxScale binlog servers)
• Orchestrator supports many different types of topologies, from a single …

I have used many tools starting with MMM to be able to manage MySQL replication clusters. Some of the tools need more tools and complex HA solutions such as Pacemaker and Corosync, or Zookeeper. While other tools do not do the failover well which leaves the slaves in an inconsistent state, MMM would be an example. And I must say that of all the tools I love MySQL Master HA (MHA) the most. MHA is a great tool to manage MySQL replication clusters for the purpose of HA. The most important thing about MHA is that it tries to take all the necessary steps to do a MySQL master failover in a way that provides as much data consistency as possible. The slave promotion also tends to be very quick, on average I have seen it take 10 to 15 seconds. It is also very easy to deploy unlike some of the other complex HA solutions. I would highly recommend reading about the architecture of MHA on its wiki: https://code.google.com/p/mysql-master-ha/wiki/Architecture Why …

In a recent post the MySQL product managers asked the community for feedback about proposed new defaults. One of the proposals is to make log-slave-updates on by default.

There are other important options that require some debate. They all look reasonable to me. This one, instead, which implies funnelling the replication events in a slave to its binary log, is questionable.

Let's start for the reason why it is a good idea. The scenario in which it makes sense is when you want a slave to be a master of one or more slaves. This is a common scenario in many cases where you need …

The default or “out of the box” experience is simply the experience for most people, so it’s critically important for us to ensure that the default configuration offers a good experience for the vast majority of cases. This is always a challenge, due to the matrix of factors involved–hardware configurations, software stacks, application use cases, etc.–but it’s most certainly a worthy endeavor.…

High Availability

Have you ever wondered if your application should be able to work in read-only mode? How important is that question?

MySQL seems to be the most popular database solution for web-based products. Most typical Internet application workloads consist of many reads, with usually few writes. There are exceptions of course – MMO games for instance – but often the number of reads is much bigger then writes. So when your database infrastructure looses its ability to accept writes, either because traditional MySQL replication topology lost its master or Galera cluster lost its quorum, why would you want to the application to declare total …

Data is the most important asset any organization has especially those who belongs to web, mobile, social, enterprise and cloud applications.

Availability refers to the ability to cope with, and if necessary recover from, failures on the host, including failures of MySQL, the operating system, or the hardware and maintenance activity that may otherwise cause downtime.

Because each application has different operational and availability requirements, MySQL offers a range of certified and supported solutions, delivering the appropriate levels of High Availability (HA). 

Factors to consider for HA Solution: 

• Operational Capabilities
• Budgetary Constraints
• The level of availability required (In terms of Time)
• The type of application being deployed
  • Mission critical services …

I am a MySQL DBA role as usual check the problems and seek a solution.
On one of the production host (MySQL v5.1.53), I started getting errors in this series:

[Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'binlog.000942' at postion 45042

[ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)

[Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'binlog.000928' at postition

[ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)

…

Some expert says you should increase the slave_net_timeout and some says to check value of  relay_log_space_limit but it is default already

slave_net_timeout = 3600
relay_log_space_limit = 0 (unlimited) 
max_allowed_packet = 128MB

I can see no heavy queries …

This blog post explores the syncing options for an inconsistent MySQL slave of Galera cluster node using pt-table-sync

The post Fixing inconsistency on MySQL Slave of Galera Cluster first appeared on Change Is Inevitable.