The slave replication process does not start mysql and starts the skip-slave-start parameter.

The slave replication process does not start mysql and starts the skip-slave-start parameter. There is a set of master and slave databases. In the early stage, only some of these databases are copied in the my. cnf configuration file. Later, due to business requirements, the database that has not been copied should also be copied. Today, after modifying the my. cnf configuration file and restarting the database, the sad thing happened. slave also started, and then began to copy, resulting in data inconsistency. The key is to reset slave from the slave database. The correct steps are as follows: 1 dump master database data and stop slave. 2. Pass it to the slave database slave and restore it on the slave database slave. 3. change master to and set slave Database Replication information for slave. 4. It is important to modify the configuration file and start the mysql database. Because I put Step 4 before step 3, the operation after Step 3 fails and the data is inconsistent. In the my. cnf configuration file, you can add this parameter skip_slave_start, so that the replication process will not start [mysqld] skip-slave-start as the database starts.