Planet MySQL

Displaying posts with tag: MySQL restart (reset)

Dec

2018

Slow MySQL Start Time in GTID mode? Binary Log File Size May Be The Issue

Posted by ScaleGrid.io on Thu 06 Dec 2018 19:30 UTC
Tags:

sql, database, monitoring, cloud, Testing, Developer, mysql server, howto, MySQL, GTID-based replication, replica set, MySQL 5.7.7, MySQL restart, MySQL Hosting, binary log file, Binary Log File Size, Database Server, database shutdown, Debug MySQL Issues, flushing the binary log files, GTID Mode, GTID system variables, gtid_executed, gtid_purged, InnoDB data files, maintenance shutdown, MySQL Start Time, mysqld process, Percona Tool, reduce the size of the binary log files, server restart, Slow MySQL, system startup time

Have you been experiencing slow MySQL startup times in GTID mode? We recently ran into this issue on one of our MySQL hosting deployments and set out to solve the problem. In this blog, we break down the issue that could be slowing down your MySQL restart times, how to debug for your deployment, and what you can do to decrease your start time and improve your understanding of GTID-based replication.

How We Found The Problem

We were investigating slow MySQL startup times on a low-end, disk-based MySQL 5.7.21 deployment which had GTID mode enabled. The system was part of a master-slave pair and was under a moderate write load. When restarting during a scheduled maintenance, we …

[Read more]

Jul

2018

Data Integrity and Performance Considerations in MySQL Semisynchronous Replication

Posted by ScaleGrid.io on Wed 11 Jul 2018 13:54 UTC
Tags:

High Availability, Developer, howto, mysql performance, MySQL, Performance, node, replica set, 3-Node Replica Set, asynchronous mode, Configurations on the Master Node, Configurations on the Slave Node, Data Consistency in MySQL, high data integrity, InnoDB Storage Engine, master binary logs, multi-threaded slaves, MySQL Configurations, MySQL Data Integrity, MySQL Master Node, MySQL replica set, MySQL restart, MySQL Semisynchronous Replication, MySQL Slave Node, slave SQL thread performance, SQL thread, SQL thread workers

MySQL semisynchronous replication provides improved data integrity because when a commit returns successfully, it’s known that the data exists in at least two places – the master and its slave. In this blog post, we review some of the MySQL hosting configurations that influence the data integrity and performance aspects of semisynchronous replication. We’ll be using InnoDB storage engine and GTID-based replication in a 3-node replica set (master and 2 slaves), which will ensure there is redundancy in the slaves. This means that if there are issues with one slave, we can fall back on the other.

Configurations Applicable to Both Master and Slave Nodes

…[Read more]

Top Authors

Oracle MySQL Blogs

Team Blogs

Vendor Blogs

Search

MySQL Links