Launch a new Slave-DB
Table of Contents
Once you've launched a new Slave-DB instance, the DB is fully operational. If INIT_SLAVE_AT_BOOT is set to false then DB contents initialization and replication start needs to be executed as a separate action using the DB EBS init slave operational script. Initializing the slave from a master involves, first creating an new EBS volume from the latest master snapshot, and then start replication from the first transaction after the copied contents. After a slave has been initialized, its contents will be in in sync with the master and the replication will be active.
Instructions
- Verify that there is at least one "completed" master snapshot created from the current master.
- Go to your deployment (Manage -> Deployments).
- Select the Volumes tab and locate the MySQL master instance and select its volume. Select the Snapshots tab for the EC2 EBS volume and verify that there is at least one snapshot that is "100% completed." If not, you will have to wait until the snapshot is 100% complete before launching a new slave.
- Go to your deployment (Manage -> Deployments).
- Locate a MySQL EBS "slave" server instance and under the Inputs tab set the input variable, INIT_SLAVE_AT_BOOT = True.
- Click the Launch button.
What feedback to expect
A notification on the Recent Events pane should indicate that the Slave-DB server is pending.
To confirm it, we can:
- Access the list of active servers (Manage -> Servers)
- Locate the new 'pending' instance.
- Click on its nickname to see its full information.
- Make sure that the template field matches the name and version you launched (e.g., MySQL Additional v?) and that the creation time matches the time you launched it.
IMPORTANT! When you are through make sure your Servers are named appropriately! For example, if you have a new master and a new slave Server, make sure you name (or rename) your Servers appropriately.
- © Copyright 2015 RightScale Technical Support