Showing entries 1 to 10 of 126
10 Older Entries »
Displaying posts with tag: mysql replication (reset)
Can we set Replication Filters per channel in Multi-Source Replication?

Multi-Source Replication is one of the awesome features in MySQL 5.7 which allows the slave to get the replication streams from multiple masters by having a replication channel for each master.
But what about the replication filters? Can we set replication filters per channel in the multi-source replication?

In brief, replication filtering is a way used to eliminate part of the master’s events (not) to be replicated to the slaves (Also known as Partial Replication). This can be done on either master (using --binlog-do-db and --binlog-ignore-db options) or slaves (using --replicate-* options) while it is not recommended on the master anyway at least to provide Point in Time Recovery (PiTR).

[Read more]
MySQL replication primer with pt-table-checksum / pt-table-sync, part 2

This is the second and last tutorial blog post on how to use pt-table-checksum / pt-table-sync tools for MySQL replication.

In the first post, I showed you how to use the

pt-table-checksum

  /

pt-table-sync

  tools in a typical MySQL replication setup. In this post, we’ll discuss MySQL replication for more advanced topologies. I will show you how to use these tools in a chained …

[Read more]
STOP SLAVE Improvements for Multi-Threaded Slaves

When using a multi-threaded slave, the STOP SLAVE command could take a long time to return because the slave waited for workers to catch up processing the queue. This blog post is about improvements that have been made in MySQL 5.6.26 and later to ensure that STOP SLAVE returns quickly when using a multi-threaded slave (MTS).…

MySQL 5.7 multi-source replication – automatically combining data from multiple databases into one

MySQL’s multi-source replication allows you to replicate data from multiple databases into one database in parallel (at the same time). This post will explain and show you how to set up multi-source replication. (WARNING: This is a very long and detailed post. You might want to grab a sandwich and a drink.)

In most replication environments, you have one master database and one or more slave databases. This topology is used for high-availability scenarios, where the reads and writes are split between multiple servers. Your application sends the writes to the master, and reads data from the slaves. This is one way to scale MySQL horizontally for reads, as you can have more than one slave. Multi-source replication allows you to write to multiple MySQL instances, and then combine the data into one server.

Here is a quick overview of …

[Read more]
Replication in MySQL 5.7 GA

MySQL 5.7 has been recently declared Generally Available and in it there is a set of new replication features. Over the last 6 years MySQL replication has evolved at a tremendous pace. MySQL 5.6 brought us a lot of new replication features, many that were ground breaking and yes, sometimes controversial.…

MySQL Router on Labs – The Newest Member of the MySQL family

The MySQL team are busily working on improving ways to use MySQL in scalable highly available systems. As most of you are already aware, the MySQL Group Replication project is progressing at full speed. Indeed, we just got preview release 0.5 out, while Fabric 1.5.6 was just released and work is ongoing for the Fabric 1.6 release.…

MySQL Group Replication: Auto-increment configuration/handling

In 0.5.0 version of MySQL Group Replication plugin, we have introduced the Auto-increment configuration/handling feature through which auto increment variables (auto_increment_increment and auto_increment_offset) are auto configured by the plugin, so that different members of the group don’t generate duplicated auto increment values.…

MySQL replication primer with pt-table-checksum and pt-table-sync

MySQL replication is a process that allows you to easily maintain multiple copies of MySQL data by having them copied automatically from a master to a slave database.

It’s essential to make sure the slave servers have the same set of data as the master to ensure data is consistent within the replication stream. MySQL slave server data can drift from the master for many reasons – e.g. replication errors, accidental direct updates on slave, etc.

Here at Percona Support we highly recommend that our customers periodically run the pt-table-checksum tool to verify data consistency within replication streams. Specifically, after fixing replication errors on slave servers to ensure that the slave has identical data as its master. As you don’t want to put …

[Read more]
Webinar-on-demand: Learn how to add HA and DR to MySQL operating on-prem and in VMware's vCloud Air public cloud

Learn how VMware Continuent adds HA, DR and real-time data warehouse loading to off-the-shelf MySQL operating on-prem and in VMware vCloud Air public cloud. 

We introduce vCloud Air basics, then do a deep dive into the VMware Continuent system architecture covering important issues like fail-over, zero-downtime maintenance, and load scaling. We will conclude with a demonstration of using

Replication in real-time from Oracle and MySQL into data warehouses and analytics

Practical tips and a live demo of how to get your data warehouse loading projects off the ground quickly and efficiently when replicating from MySQL and Oracle into Amazon Redshift, HP Vertica and Hadoop.

Webinar-on-demand. Recorded 07/23/15.

Showing entries 1 to 10 of 126
10 Older Entries »