Enterprise case "Troubleshooting" MySQL master-Slave fault resolution process

Due to the configuration of Zabbix monitoring, a day received Zabbix monitoring master-Slave Alarm, view the MySQL status,

Showslave status \g;

SLAVE replication status is incorrect, slave_sql_running is no,

Then look at the following error message, prompting for a table to insert data, indicating that the table does not exist,

Then check the library from the library that the table, found all stored, just wonder.

And then back to the newspaper wrong there is a new discovery, the hint is uppercase, I just checked the lowercase,

OK, again into the database from the use of Uppercase query table, sure enough error, it appears that the case is caused by the problem.

Data found MySQL parameters have ignored case-sensitive parameters Lower_case_table_names=1

Decisive changes in the [MYSQLD] block added This parameter is, at the same time there is a heart to see the configuration of the main library, found that the main library has this configuration

Should be the problem here, this time restart from the library, view slave status, found the error hour, both states are yes, continue to copy operations.

Summarize:

Final summary reason: slave-end MY.CNF configuration is missing Lower_case_table_names=1 caused. Therefore, the master-slave configuration must pay attention to configuration parameters.

Enterprise case "Troubleshooting" MySQL master-Slave fault resolution process