Slave Applier

The slave applier plugin, named slave, provides a native implementation of replication between Drizzle servers by applying replication events from multiple “master” servers to a “slave” server. A slave is a server on which the slave plugin is loaded, configured, and ran. Slaves can connect to up to ten masters at once over the network and pair with the Default Replicator on each them. Slaves apply every replication event from every master; conequently, they contain the same schemas and data as their masters.

Replication chains are supported: slaves can also be masters and replicate events to other slaves. There is no limit to the number of levels in which masters and slaves can be enchained.

Replication circles, or master-master replication, are not currently supported. Replication will break on one of the masters if this is attempted.

The next two sections, Slave Configuration and Slave Administration, contain necessary information for configuring and administering slave-based replication. The third section, Slave Details, covers technical details about how the slave plugin and slave-based replication work.

• Slave Configuration
  • Configuring a Master
  • Configuring a Slave
• Slave Administration
  • Slave Threads
  • sys_replication Tables
  • Slave Lag
  • Master Connections
  • InnoDB Transaction Log
• Slave Details
  • Slave Plugin Class

Version

This documentation applies to slave 1.1 (Drizzle 7.1).

To see which version of the slave plugin a Drizzle server is running, execute:

SELECT MODULE_VERSION FROM DATA_DICTIONARY.MODULES WHERE MODULE_NAME='slave'

Changelog

• slave Changelog
  • slave 1.1 (Drizzle 7.1)
  • slave 1.0 (Drizzle 7.0)

Authors

David Shrewsbury

Original slave plugin code. Multi-master code.

Daniel Nichter

Documentation for slave 1.1 (Drizzle 7.1).