Understanding MaxScale's Binlog Router
This page is part of MariaDB's Documentation.
The parent of this page is: Binlog Router
Topics on this page:
Overview
MaxScale's Binlog Router (binlogrouter) allows MaxScale to act as a binlog server. The router can help mitigate the effect of primary failures in deployments. If the primary fails, then the replicas can simply continue replicating existing data from MaxScale. This can also reduce the bandwidth requirements of the primary server in an environment that has a lot of replica servers, since each replica server does not have to download every individual transaction from the primary server. Instead, the primary server only sends a single copy of each transaction to MaxScale, and each replica server replicates the transaction from MaxScale.
What Does the Binlog Router Support?
The Binlog Router (readwritesplit) supports:
Replicating from deployments
Replicating from deployments
When to Use the Binlog Router?
The Binlog Router (binlogrouter) allows you to:
Mitigate the effect of primary failures by using MaxScale as a Binlog Server.
Reduces bandwidth requirements of primary server in environments with many replica servers.
Next steps: