- 16.1.1 How to Set Up Replication
- 16.1.1.1 Creating a User for Replication
- 16.1.1.2 Setting the Replication Master Configuration
- 16.1.1.3 Setting the Replication Slave Configuration
- 16.1.1.4 Obtaining the Master Replication Information
- 16.1.1.5 Creating a Data Snapshot Using mysqldump
- 16.1.1.6 Creating a Data Snapshot Using Raw Data Files
- 16.1.1.7 Setting Up Replication with New Master and Slaves
- 16.1.1.8 Setting Up Replication with Existing Data
- 16.1.1.9 Introducing Additional Slaves to an Existing Replication Environment
- 16.1.1.10 Setting the Master Configuration on the Slave
The only option you must configure on the slave is to set the unique server ID. If this option is not already set, or the current value conflicts with the value that you have chosen for the master server, then you should shut down your slave server, and edit the configuration to specify the server ID. For example:
[mysqld] server-id=2
If you are setting up multiple slaves, each one must have a
unique server-id value that
differs from that of the master and from each of the other
slaves. Think of server-id values as
something similar to IP addresses: These IDs uniquely identify
each server instance in the community of replication partners.
If you do not specify a server-id
value, it defaults to 0.
Note
If you omit server-id (or set
it explicitly to 0), a master refuses connections from all
slaves, and a slave refuses to connect to a master. Thus,
omitting server-id is good only
for backup with a binary log.
You do not have to enable binary logging on the slave for replication to be enabled. However, if you enable binary logging on the slave then you can use the binary log for data backups and crash recovery on the slave, and also use the slave as part of a more complex replication topology (for example, where the slave acts as a master to other slaves).
User Comments
Add your own comment.