This article is a part of our Rockstar DBA initiative, a platform for thought leaders to share their knowledge and make a positive contribution towards the database management community.

Manojit Paul, with more than 19 years of professional DBA experience in enterprise database solutions, especially Sybase product set and database infrastructure is our first Rockstar DBA.

Let’s hear from Manojit about how he manages MySQL databases, why he loves MONyog, his advice to young DBA’s and more.

How do you manage your MySQL databases?
We presently have 9 MySQL servers in production trading environment, all being managed via a host of automated scripts which I’ve created and manual intervention when issues are reported. We deploy MONyog for managing 5 of these critical MySQL instances. …

From previous articles about “disk full” conditions, you have some taste of testing MySQL with such approach:

1. Testing Disk Full Conditions

2. Using GDB, investigating segmentation fault in MySQL

But there is still untouched topic, about read-only mounted file system and how MySQL will act in such condition. In real life, i have encountered such situation that something happened with Linux server and file system suddenly goes to read-only mode.

Buffer I/O error on device sdb1, logical block 1769961 lost page write due to I/O error on sdb1 sd 0:0:1:0: timing out command, waited 360s sd 0:0:1:0: Unhandled error code sd 0:0:1:0: SCSI error: return code = 0x06000008 Result: hostbyte=DID_OK …

Foto: Ana Rey CC-BY-SA-2.0El “Concurso Universitario de Software Libre” (CUSL) es una iniciativa similar a la del Google Summer of Code, pero específicamente dirigida la comunidad universitaria y de estudiantes de bachillerato españoles y organizada por una grupo de Oficinas de software libre de universidades.

Como parte del esfuerzo para promover el crecimiento del ecosistema del software libre, así como introducir a talento joven en el desarrollo de aplicaciones y tecnologías libres, DBAHire.com acaba de convertirse en patrocinador plata de la competición, proporcionando recursos para los premios, gastos de …

There are tools like pt-kill from the percona tool kit that may print/kill the long running transactions at MariaDB, MySQL or at Percona data instances, but a lot of backup scripts are just some simple bash lines.
So checking for long running transactions before the backup to be executed seems to be a step that is missed a lot.

Here is one line that might be just added in every bash script before the backup to be executed
Variant 1. Just log all the processlist entries and calculate which ones were running longer than TIMELIMIT:

$ export TIMELIMIT=70 && echo "$(date) : check for long runnig queries start:" >> /tmp/processlist.list.to.kill && mysql -BN -e 'show processlist;' | tee -a /tmp/processlist.list.to.kill | awk -vlongtime=${TIMELIMIT} '($6>longtime){print "kill "$1";"}' | tee -a /tmp/processlist.list.to.kill

Variant 2: Log all the processlist, calculate the calculate which processes are …

In version MySQL 5.7.7 Oracle presented a new promising feature: optimizer hints. However it did not publish any documentation about the hints. The only note which I found in the user manual about the hints is:

• It is now possible to provide hints to the optimizer by including /*+ ... */ comments following the SELECT, INSERT, REPLACE, …

Podcasts Learning

In this penultimate episode, we talk about what's coming in MySQL 5.7 and MariaDB 10.1. Ear Candy is about a new MySQL 5.7 utility to generate the SSL RSA keys to encrypt MySQL communications, and At the Movies is about MySQL's new features.

Podcasts Learning

In this penultimate episode, we talk about what's coming in MySQL 5.7 and MariaDB 10.1. Ear Candy is about a new MySQL 5.7 utility to generate the SSL RSA keys to encrypt MySQL communications, and At the Movies is about MySQL's new features.

Today, oCERT published advisory 2015-003 describing a TLS vulnerability in MySQL and derivative products.  The content isn’t exactly news – it is documented legacy behavior and the subject of an earlier blog post describing how MySQL Server 5.7 solves the problem.  That said, the efforts of Duo Security are certainly appreciated and welcomed – it provides a meaningful context to discuss how to properly harden existing MySQL 5.5 and 5.6 deployments, as well as frame a discussion on potential changes in these versions to increase security.

Vulnerability

The vulnerability described in the advisory relies on the legacy behavior of the client …

Since VividCortex launched its database monitoring platform, many users have requested some type of notification system. To address this, we took particular care in building a feature that proactively warns users of potential problems without sending multiple false alerts.

We are excited to announce notifications via email, PagerDuty and VictorOps. This post addresses basic functionalities, but please explore the feature and provide feedback to support@vividcortex.com.

What triggers a notification? Our events dashboard records behaviors such as high swap activity, disc faults, replication stopping, mysql server restarts and more. These events are grouped into incidents based on host and type. Depending on your systems, one or more of these may signal that you need to investigate further.

Do I have control over notifications? Of course. The last thing we want is an endless flow of useless …

A few days ago I wrote up my thoughts about the Percona acquisition of Tokutek with respect to TokuDB. In this blog I'm going to do the same for TokuMX and TokuMXse. And in a few days I'll wrap up this trilogy by sharing my thoughts about Fractal Tree Indexes.

Again, when I'm writing up something that I was very involved with in the past I think it's important to disclose that I worked at Tokutek for 3.5 years (08/2011 - 01/2015) as VP/Engineering and I do not have any equity in Tokutek or Percona.

Since much of the MySQL crowd might be hearing about Tokutek's "other products" for the first time I'll provide a little history of both of the products before I dive in deeper.

TokuMX is a fork of MongoDB …