Showing entries 31 to 40 of 244
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: High Availability (reset)
State of automated recovery via Pseudo-GTID & Orchestrator @ Booking.com

This post sums up some of my work on MySQL resilience and high availability at Booking.com by presenting the current state of automated master and intermediate master recoveries via Pseudo-GTID & Orchestrator.

Booking.com uses many different MySQL topologies, of varying vendors, configurations and workloads: Oracle MySQL, MariaDB, statement based replication, row based replication, hybrid, OLTP, OLAP, GTID (few), no GTID (most), Binlog Servers, filters, hybrid of all the above.

Topologies size varies from a single server to many-many-many. Our typical topology has a master in one datacenter, a bunch of slaves in same DC, a slave in another DC acting as an …

[Read more]
Thoughts on MaxScale automated failover (and Orchestrator)

Having attended a talk (as part of the MariaDB Developer Meeting in Amsterdam) about recent developments of MaxScale in executing automated failovers, here are some (late) observations of mine.

I will begin by noting that the project is stated to be pre-production, and so of course none of the below are complaints, but rather food for thought, points for action and otherwise recommendations.

Some functionality of the MaxScale failover is also implemented by orchestrator, which I author. Orchestrator was built in production environments by and for operational people. In this respect it has gained many insights and had to cope with many real-world cases, special cases …

[Read more]
MySQL Group Replication now on more platforms

A new version of the Group Replication plugin for MySQL is available now. The newest release is available on Mac OS X, Solaris, and FreeBSD.

Additional platform support has been made possible via a new group communication implementation. This new communication system supports communication of messages between servers on many platforms, allowing MySQL to embrace the diversity of the MySQL community and enables Group Replication for more people on more platforms.…

Replication in MySQL 5.7 GA

MySQL 5.7 has been recently declared Generally Available and in it there is a set of new replication features. Over the last 6 years MySQL replication has evolved at a tremendous pace. MySQL 5.6 brought us a lot of new replication features, many that were ground breaking and yes, sometimes controversial.…

Announcing: MySQL Fabric 1.6.2 on Labs

The MySQL Fabric team is pleased to announce that a new version is now available on Labs. This labs release includes our latest developments to give you a taste of what we have been working on. In particular, it includes the following new features and improvements:

  • Multi-node Fabric support is now available! This means that multiple fabric nodes can be started and any node can be contacted to perform operations. This allows Fabric itself to be fault-tolerant (no single point of failure) and distribute request across multiple Fabric nodes. For more information, see: Increasing MySQL Fabric Resilience to Failures: Meet the Multi-Node Fabric 
  • Improved security password management, allowing password to not be passed in plain text in the command line or configuration files. …
[Read more]
Increasing MySQL Fabric Resilience to Failures: Meet the Multi-Node Fabric

Overview

Redundancy is key to providing resilience to failures, and in Fabric 1.6.2 (now available on MySQL Labs), we have introduced the possibility to start multiple MySQL Fabric instances that are kept consistent through a replicated state machine.

The state machine replication guarantees that all machines (i.e.…

Announcing: MySQL Fabric 1.6.2 on Labs

The MySQL Fabric team is pleased to announce that a new version is now available on Labs. This labs release includes our latest developments to give you a taste of what we have been working on. In particular, it includes the following new features and improvements:

  • Multi-node Fabric support is now available!

Remove a Galera (Percona Cluster) Node During Backup

With Galera (Percona Cluster or MariaDB Cluster), it is sometimes advisable to not route traffic to a node during a backup due to the node already being under a heavier load.  In these situations, it may be wise to not route traffic there until the backup is complete.

Since the default /usr/bin/clustercheck script did not have the option of doing this, we created a modified version.  The below script looks for the presence of the xtrabackup tool running in the process list.  If it is found, the clustercheck script returns the appropriate exit code (502) which signals the load balancer to not route traffic its way.  The script could easily be modified to look for the presence of programs/tools in the process list.

We hope others will find it useful.

#!/bin/bash
# clustercheck.sh
#
# Script to make a proxy (ie HAProxy) capable of monitoring Percona XtraDB Cluster nodes properly
#
# Modified by Itchy …
[Read more]
Easy Load-balancing and High-availability using MySQL Router

The newest member of the MySQL family, the MySQL Router, was released on labs.mysql.com just a few days ago. In the two previous posts, you could see what kind of features that are currently available as well as how to compile and install the MySQL Router.…

MySQL Health Check Script

Ever get called out for a MySQL issue only to realize that there was no issue?  It was a false alarm from the monitor.  We sure have and it’s frustrating, especially at 3:00 or 4:00 in the morning!

Many DBAs work in an environment where there is some sort of first level support that gets assigned tickets first.  Unfortunately, many of the times these groups are, shall we say, less than skilled in MySQL.  As a result, they quickly escalate the ticket onto the primary on-call DBA, even when there is really nothing wrong.

Much of the time, there are multiple types of MySQL topology in these environments: standalone, galera cluster, replication, etc.  Writing large runbooks with detailed test cases can be a daunting process and one that will cause many first-level support engineers to give up and simply escalate the issue anyway.

In an effort to avoid undue call outs, we developed a simple bash …

[Read more]
Showing entries 31 to 40 of 244
« 10 Newer Entries | 10 Older Entries »