MySQLbug: server-id is automatically set to 1 by default. When my colleague called the master node yesterday, the slave database reported the following error: Gotfatalerror1236frommasterwhenreadingdatafrombinarylog: Misconfiguredmaster.
MySQL bug: the server-id is automatically set to 1 by default. when a colleague called the master node yesterday, the slave database reported the following error: Got fatal error 1236 from master when reading data from binary log: 'misconfigured master-server id was not set' is crude. It looks like the master's server-id is not set, but my colleagues do the following:
MySQL bug: server-id is automatically set to 1 by default
When my colleague called the master node yesterday, the slave database reported the following error:
Got fatal error 1236 from master when reading data from binary log: 'Misconfigured master - server id was not set'
The rough look is like the master's server-id is not set, but colleagues do the following query:
Slave database collection: root @ localhost Fri May 23 14:18:59 2014 14:18:59 [(none)]> show variables like '% server_id % '; + --------------- + ------- + | Variable_name | Value | + --------------- + ------- + | server_id | 2 | + --------------- + ------- + master database collection: mysql> show variables like '% server % '; + servers + ----------------- + | Variable_name | Value | + servers + ------------------- + | character_set_server | latin1 | collation_server | latin1_swedish_ci | server_id | 1 | + servers +
In this case, the server-id of the replication environment is indeed globally unique. Why is an error reported?
Because the business is used to store hadoop metadata, MySQL version was earlier, and my colleagues used slave higher than the master version, this was the reason, but on the MySQL bug list, we found:
This discovery denies our previous judgment. After testing by a colleague, it is indeed the bug :-)
Have a good weekend,
Good Luck!