The Replicator is a critical piece of the Tungsten Clustering solution for MySQL / MariaDB, as well as its own stand-alone data replication product. Automatic recovery is a feature that enables the Replicator to go back online in the event of a transient failure. In this blog we discuss how to enable Automatic Recovery. For more information about Auto-Recovery, please click here to visit the online documentation page.

The Question Recently, a customer asked us:

We see that the replicators receive a transaction which has a deadlock error in it:

pendingError : Event application failed: seqno=82880882 fragno=0 message=java.sql.SQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction

If one performs a service online, it comes back online without issue and continues …

Migrations between different environments are uncommon in database world. Migrations from one provider to another one. Moving from one datacenter to another. All of this happens on a regular basis. Organisations search for expense reduction, better flexibility and velocity. Those who owned their datacenter look forward to switch to one of the cloud providers where they can benefit from better scalability and handling capacity changes. Migrations touch all elements of the database environment - databases themselves but also the proxy and caching layer. Moving databases around is tricky but it is also hard to manage multiple proxy instances, ensuring that the configuration is in sync across all of them.

In this blog post we will take a look at challenges related to one particular piece of migration - migrating ProxySQL proxy layer from …

Late one evening, I was staring at one of our large MySQL installations and noticed the database was hovering around 7-10 run queue length (48 cores, ~500 gigs memory, fusionIO cards). I had been scratching my head on how to get more throughput from the database. This blog records the changes I made to tune performance in order to achieve a 300% better throughput in MySQL. I tested my theories on MySQL 5.6/Maria 10.1. While with 5.7 DBAs would turn to performance_schema for the supporting metrics, I hope that you find the process interesting nevertheless.

View from an Oracle RDBMS DBA…

For context, I came to MySQL from a background as an Oracle RDBMS DBA, and this informs my expectations. For this exercise, unlike with Oracle RDBMS, I had no access to view wait events so that I could see where my database was struggling. At least, no access in MySQL 5.6/Maria 10.1 without taking a performance hit by using …

FromDual has the pleasure to announce the release of the new version 2.2.1 of its popular Backup and Recovery Manager for MariaDB and MySQL (brman).

The new FromDual Backup and Recovery Manager can be downloaded from here. The FromDual Repositories were updated. How to install and use the Backup and Recovery Manager is describe in FromDual Backup and Recovery Manager (brman) installation guide.

In the inconceivable case that you find a bug in the FromDual Backup and Recovery Manager please report it to the FromDual Bugtracker or just send us an …

Author: Robert Agar

In the complicated world of database management, a lot of data needs to be assimilated by those responsible for keeping the systems healthy and operational. Management and the database team can be challenged trying to stay on top of all the moving parts required to keep things running smoothly. This task can prove to be quite difficult when faced with a large number of databases which may encompass several diverse platforms.

There are many different database products from which to choose. Some are more appropriate for particular uses which may play a role in your decision to go with one solution over another. Open-source databases are very popular, and MySQL has a large lead in the number of users it supports. It is the top-ranked open-source database in terms of popularity. When …

Database Administration is a tough, often ungrateful job. Especially if you run a 24/7 business-critical MySQL or MariaDB deployment.

MySQL has proven to be a remarkably solid database which supports billions of dollars in revenue. On some level this very solidity creates a false sense of security. There are many things that can wrong at any given time, whether that is a change to your app, a bug in the database, hardware failure or just simply running out of disk space.

Percona recently conducted a poll: “What keeps you up at night?”

Not surprisingly, “Downtime/HA” is very high on the list.

While there are many challenging issues and tasks that a DBA must deal …

Please join Percona CEO Peter Zaitsev as he presents “Performance Analyses and Troubleshooting Technologies for Databases” on Wednesday, August 7th, 2019 at 11:00 AM PDT (UTC-7).

Register Now

Have you heard about the USE Method (Utilization – Saturation – Errors), RED (Rate – Errors – Duration) or Golden Signals (Latency – Traffic – Errors – Saturations)?

In this presentation, we will talk briefly about these different-but-similar “focuses” and discuss how we can apply them to data infrastructure performance analysis troubleshooting and monitoring.

We will use MySQL as an example, but most of this talk applies to other database technologies as well.

…

Data is an invaluable asset to any organisation and every data should not be viable to all DB users. I had a requirement from one of our Support client to hide (mask) a few columns to the end user. Those columns contains sensitive information like payment details and mobile numbers.

In this blog post I am going to explain the how data masking features in Maxscale can be benefitted in such use case.

Maxscale Masking

Masking filter was introduced on the Maxscale 2.1 version . Below is a simple scenario. The columns “name” and “mobile” from the table student has to be masked.

[root@labs7.mydbops.com ~]# maxscale --version                                                           MaxScale 2.3.6

#Table Structure 

mysql> show create table student\G
*************************** 1. row ***************************
       Table: …

This week is our pleasure to remind following shows where you can find MySQL & MySQL Community experts: 

• Kansas Linux Fest (KLF), Wichita, Kansas City, US, August 9-11, 2019

  • Do not miss to listen MySQL talks given by David Stokes, the MySQL Community Manager as follows:
    • "MySQL Without the SQL - Oh My!"
    • "The Proper Care and Feeding of a MySQL Database for Busy Linux Administrators"
  • Watch the organizers' website for timing and place!
• FrOSCon 2019, Snkt. Augustin, Germany, August 10-11, 2019
  • Come to talk to us to our MySQL booth and do not miss the talk by Carsten Thalheimer, the MySQL …

Database Reliability Engineering – How to decide RAID for your Database Infrastructure ? What is RAID?

RAID stands for Redundant Array of Independent Disks (Originally, the term RAID was defined as Redundant Array of Inexpensive Disks). The name indicates that the disk drives are independent, and are multiple in number. RAID storage uses multiple disks in order to provide fault tolerance, to improve overall performance, and to increase storage capacity in a system. This is in contrast with older storage devices that used only a single disk drive to store data.How the data is distributed between these drives depends on the RAID level used. The main advantage of RAID, is the fact that, to the operating system the array of disks can be presented as a single disk.RAID is fault tolerant because in most of the RAID level’s data is redundant in multiple disks, so …