mysql5.6搭建主从过程中遇到主从server_uuid一致无法同步的问题
| Property | Value |
|---|---|
| System Variable | server_uuid |
| Scope | Global |
| Dynamic | No |
| Type | string |
When starting, the MySQL server automatically obtains a UUID as follows:
-
Attempt to read and use the UUID written in the file data_dir/auto.cnf (where data_dir is the server's data directory).
-
If data_dir/auto.cnf is not found, generate a new UUID and save it to this file, creating the file if necessary.
The auto.cnf file has a format similar to that used for my.cnf or my.ini files. In MySQL 5.6, auto.cnf has only a single [auto] section containing a single server_uuid setting and value; the file's contents appear similar to what is shown here:
[auto]server_uuid=8a94f357-aab4-11df-86ab-c80aa9429562
The auto.cnf file is automatically generated; do not attempt to write or modify this file.
In MySQL 5.6.5 and later, a server's server_uuid is also used in GTIDs for transactions originating on that server. For more information
When starting, the slave I/O thread generates an error and aborts if its master's UUID is equal to its own unless the --replicate-same-server-id option has been set.
错误如下：
Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs; these UUIDs must be different for replication to work.
解决方法：
cd $MYSQL_DATA_HOME/data/
mv auto.cnf auto.cnf.bk
重启mysql即可
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/29802484/viewspace-2153807/ ，如需转载，请注明出处，否则将追究法律责任。
