Book Image

MySQL 8 Cookbook

By : Karthik Appigatla
Book Image

MySQL 8 Cookbook

By: Karthik Appigatla

Overview of this book

MySQL is one of the most popular and widely used relational databases in the World today. The recently released MySQL 8 version promises to be better and more efficient than ever before. This book contains everything you need to know to be the go-to person in your organization when it comes to MySQL. Starting with a quick installation and configuration of your MySQL instance, the book quickly jumps into the querying aspects of MySQL. It shows you the newest improvements in MySQL 8 and gives you hands-on experience in managing high-transaction and real-time datasets. If you've already worked with MySQL before and are looking to migrate your application to MySQL 8, this book will also show you how to do that. The book also contains recipes on efficient MySQL administration, with tips on effective user management, data recovery, security, database monitoring, performance tuning, troubleshooting, and more. With quick solutions to common and not-so-common problems you might encounter while working with MySQL 8, the book contains practical tips and tricks to give you the edge over others in designing, developing, and administering your database effectively.
Table of Contents (20 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Setting up semi-synchronous replication


Replication is asynchronous by default. The master is not aware of whether the writes have reached the slaves or not. If there is a delay between master and slave, and if the master crashes, you will lose the data that has not reached the slave. To overcome this situation, you can use semi-synchronous replication.

In semi-synchronous replication, the master waits until at least one slave has received the writes. By default, the value of rpl_semi_sync_master_wait_point is AFTER_SYNC; this means that the master syncs the transaction to the binary log, which is consumed by the slave.

After that, the slave sends an acknowledgement to the master, then the master commits the transaction and returns the result to the client. So, it is enough if the writes have reached the relay log; the slave need not commit the transaction. You can change this behavior by changing the variable rpl_semi_sync_master_wait_point to AFTER_COMMIT. In this, the master commits the...