This is Part #2 of the MySQL Master Replication Crash Safety series. In the previous post, we explored the consequence of reducing durability on masters with slaves using legacy file+position replication. The consequences are data inconsistencies with a clear warning sign: the slaves stop replicating and report an error. In this post, we extend our understanding of the impact of running a master with sync_binlog != 1 by considering lagging slaves that are using file+position replication. This introduces a new inconsistency scenario without replication breakage, which is trickier to detect. But let's start with some reminders.
Thursday, November 15, 2018
Tuesday, November 13, 2018
In the last few months, I had to install Percona Server 5.7 (PS5.7) on Debian a few times. I was regularly annoyed by apt-get -y install percona-server-server-5.7 prompting me for a password. But that annoyance did not push me to investigate the subject in detail: it was always a quick manual fix and Googling did not lead to a straightforward solution. However in the last days, I had to install PS5.7 on many servers, so it was worth finding how to do this. I am writing this post in the hope that it will help some people...