Tag: MySQL Replication

Feed: Planet MySQL; Author: Tony Darnell; Adding a replicated MySQL database instance using a Group Replication server as the source March 25, 2019 Leave a comment You say you want a Replication? One of the best features of MySQL is the ability to use MySQL‘s built-in database replication feature to automatically replicate data from one server (source/master) to another (slave/replica). Group Replication was added in MySQL 5.7 as a way to provide a high-availability solution using a new variation of MySQL replication. (In some earlier posts, I explained how to setup Group Replication using three MySQL database servers and how to ... Read More

Feed: Planet MySQL; Author: Severalnines; ProxySQL is an intelligent and high-performance SQL proxy which supports MySQL, MariaDB and ClickHouse. Recently, ProxySQL 2.0 has become GA and it comes with new exciting features such as GTID consistent reads, frontend SSL, Galera and MySQL Group Replication native support. It is relatively easy to run ProxySQL as Docker container. We have previously written about how to run ProxySQL on Kubernetes as a helper container or as a Kubernetes service, which is based on ProxySQL 1.x. In this blog post, we are going to use the new version ProxySQL 2.x which uses a different ... Read More

Feed: Planet MySQL; Author: Severalnines; The following is an excerpt from our whitepaper “How to Design Highly Available Open Source Database Environments” which can be downloaded for free. A Couple of Words on “High Availability” These days high availability is a must for any serious deployment. Long gone are days when you could schedule a downtime of your database for several hours to perform a maintenance. If your services are not available, you are losing customers and money. Therefore making a database environment highly available has typically one of the highest priorities. This poses a significant challenge to database administrators ... Read More

Feed: Planet MySQL; Author: Severalnines; Galera replication is relatively new if compared to MySQL replication, which is natively supported since MySQL v3.23. Although MySQL replication is designed for master-slave unidirectional replication, it can be configured as an active master-master setup with bidirectional replication. While it is easy to set up, and some use cases might benefit from this “hack”, there are a number of caveats. On the other hand, Galera cluster is a different type of technology to learn and manage. Is it worth it? In this blog post, we are going to compare master-master replication to Galera cluster. Replication ... Read More

Feed: Planet MySQL; Author: Severalnines; Long gone are the days when a database was deployed as a single node or instance - a powerful, standalone server which was tasked to handle all the requests to the database. Vertical scaling was the way to go - replace the server with another, even more powerful one. During these times, one didn’t really have to be bothered by network performance. As long as the requests were coming in, all was good. But nowadays, databases are built as clusters with nodes interconnected over a network. It is not always a fast, local network. With ... Read More

Feed: Planet MySQL; Author: Shlomi Noach; We are pleased to release gh-mysql-rewind, a tool that allows us to move MySQL back in time, automatically identify and rewind split brain changes, restoring a split brain server into a healthy replication chain. I recently had the pleasure of presenting gh-mysql-rewind at FOSDEM. Video and slides are available. Consider following along with the video. Motivation Consider a split brain scenario: a "standard" MySQL replication topology suffered network isolation, and one of the replicas was promoted as new master. Meanwhile, the old master was still receiving writes from co-located apps. Once the network isolation ... Read More

Feed: Planet MySQL; Author: Lalit; Replication used to replicate data from the Master node to a slave node[Replica].By default Replication is asynchronous.It uses binary logs for reading data from the Master node and relay log on slave[Replica].Depending on the configuration, you can replicate all databases, selected databases, or even selected tables within a database.Replication Methods:File-based Replication:The traditional method is based on replicating events from the master’s binary log, and requires the log files and positions in them to be synchronized between master and slave.GTID Replication:The newer method based on global transaction identifiers (GTIDs) is transactional and therefore does not require working with ... Read More

Feed: Planet MySQL; Author: Jean-François Gagné; Some months ago, Shlomi Noah 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 failover 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 Orchestrator, and even if you are not fully automating the process yet.  Taking a step back, I realized that service discovery is only one of the five parts of a full MySQL Master ... Read More

Feed: Planet MySQL; Author: MyDBOPS; Recently we had encountered a strange issue with replication and temp directory(tmpdir) change while working for one major client. All the servers under this were running with Percona flavor of MySQL versioned 5.6.38 hosted on a Debian 8(Jessie) The MySQL architecture setup  is as follows one master with 5 direct slaves under it Through this blog, we will take you through the issue we had faced and how we fixed ultimately. Client Request: There was a simple request from our client to add a column and index to a 16GB production table since the table ... Read More

Feed: Planet MySQL; Author: MySQL Performance Blog; PREVIOUS POST Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL®, MongoDB®, and PostgreSQL performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL®, MongoDB®, and PostgreSQL® servers to ensure that your data works as efficiently as possible. In this release, we are introducing support for detection of our upcoming PMM 2.0 release in order to avoid potential version conflicts in the future, as PMM 1.x will not be compatible with PMM 2.x. Another improvement in ... Read More