mysql5.6搭建主從過程中遇到主從server_uuid一致無法同步的問題怎么解決

本篇內容介紹了“mysql5.6搭建主從過程中遇到主從server_uuid一致無法同步的問題怎么解決”的有關知識，在實際案例的操作過程中，不少人都會遇到這樣的困境，接下來就讓小編帶領大家學習一下如何處理這些情況吧！希望大家仔細閱讀，能夠學有所成！

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.
<table frame="box" rules="all" summary="Properties for server_uuid" ">

When starting, the MySQL server automatically obtains a UUID as follows:

1. Attempt to read and use the UUID written in the file data_dir/auto.cnf (where data_dir is the server's data directory).

2. 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一致無法同步的問題怎么解決”的內容就介紹到這里了，感謝大家的閱讀。如果想了解更多行業相關的知識可以關注億速云網站，小編將為大家輸出更多高質量的實用文章！