本篇内容介绍了“MySQL5.6搭建主从过程中遇到主从server_uuid一致无法同步的问题怎么解决”的有关知识，在实际案例的操作过程中，不少人都会遇到这样的困境，接下来就让小编带领大家学习一下如何处理这些情况吧！希望大家仔细阅读，能够学有所成！
创新互联专注于企业全网营销推广、网站重做改版、双清网站定制设计、自适应品牌网站建设、H5开发、商城开发、集团公司官网建设、外贸网站制作、高端网站制作、响应式网页设计等建站业务，价格优惠性价比高，为双清等各大城市提供网站开发制作服务。
Beginning with MySQL 5.6, the server generates a true UUID in addition to the --server-id supplied by the user. This is available as the global, read-only variable 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
Important
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即可
“mysql5.6搭建主从过程中遇到主从server_uuid一致无法同步的问题怎么解决”的内容就介绍到这里了，感谢大家的阅读。如果想了解更多行业相关的知识可以关注创新互联网站，小编将为大家输出更多高质量的实用文章！
