Some months ago, Shlomi Noach published a series about Service Discovery. In his posts, Shlomi describes many ways for an application to find the master. He also gives detail on how these solutions cope with failing-over to a slave, including their integration with Orchestrator.
This is a great series, and I recommend its reading for everybody implementing master failover, with or without
This is a follow-up post in the MySQL Master Replication Crash Safety series. In the two previous posts, we explored the consequence of reducing durability on masters (including setting sync_binlog to a value different than 1) when slaves are using legacy file+position replication. In this post, we cover GTID replication. This introduces a new inconsistency scenario with a potential
A colleague brought an article to my attention. I did not see it on Planet MySQL where I get most of the MySQL news (or it did not catch my eye there). As it is interesting replication stuff, I think it is important to bring it to the attention of the MySQL Community, so I am writing this short post.
The surprising part for me is that it uses my 4-year-old work for online migration to GTID
MySQL 8.0.1 is out and it includes an implementation of my feature request (Bug #77438). This extension to RESET MASTER allows to simplify master promotion with Binlog Servers. Let's see how it works:
# mysql -N <<< "SHOW MASTER STATUS" binlog.027892 3006935 # mysql -N <<< "RESET MASTER TO 12345; DO sleep(rand()*10); SHOW MASTER STATUS" binlog.012345 92773 # mysql -N <<< "RESET MASTER TO
This year, Percona introduced Community Voting for Percona Live submission. This is what you can read on the conference website:
In an effort to involve the larger community in the selection of speaking sessions for the 2016 Percona Live Data Performance Conference, we’ve implemented a community voting process. After a speaker submits a proposal we encourage sharing to the community and social
A common way to implement point in time recovery capability is:
to regularly do a full backup of a database, and to save the binary logs of that database (or from its master if doing backups on a slave).
When point in time recovery is required you need to:
restore a backup, and apply the binary logs up to the point of recovery.
(Step # 2 and # b above are the ones that will be simplified
http://blog.booking.com/abstracting_binlog_servers_and_mysql_master_promotion_wo_reconfiguring_slaves.html
Follow the link above to read my latest article on the Booking.com Developer Blog. It is about Binlog Servers and how to promote a slave as the new master without reconfiguring all slaves.
This is also a good opportunity to remind you of my next talks:
I’ll be giving a talk about Binlog
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
The link to the slides of my talks can be found at the end of
this post but first, let me share some thoughts about PLMCE.
Talking with people, I was surprised to be criticized of
presenting only the good sides of my solution without giving
credit to the good side of the alternative solutions. More
than surprised, I was also a little shocked as I want to be
perceived as objective as possible. Let me try to fix
that:
Updated 2015-04-25: add the link to the slides of my PLMCE talk and a link to a bug number.
MaxScale 1.1.0 is out and includes the new Binlog Server module. This is the first post in s series of three. The two others are about Operations and High Availability. The links to the 2 other posts are at the end of this page.
In this post, I present how to install and configure MaxScale as a Binlog