The MySQL server used by the Gateway appliance uses an integer value (the server ID)to uniquely identify nodes in a cluster among each other. If these identifiers are not unique among all nodes in the cluster the MySQL replication will fail the next time the MySQL server is restarted. Replication failures can result in data loss if not addressed appropriately and put the Gateway in a degrated state.
If the databases in the Gateway cluster are not configured with unique identifiers then the following error messages will occur ;
Query the status of replication on both nodes: mysql -e "show slave status\G"
Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).
The MySQL server configuration file (my.cnf) contains a configuration directive that specifies the unique identifier for each MySQL server. The following is an excerpt from a Gateway appliance that has MySQL replication configured and enabled:
In order to resolve this issue, ensure that each database node in the cluster has a unique value for the "uncommented" server-id directive. Make any necessary changes and then restart the MySQL server. Once the MySQL server restarts, verify the status of replication via the SHOW SLAVE STATUS query. If replication reports the following messages then replication is restored:
If replication reports any other running state for MySQL replication then please review the article on how to :
Applies For 9.x Gateway Versions Only : https://knowledge.broadcom.com/external/article?articleId=44402
Applies for V10 Gateway Versions : How to Restart replication for Gateway 10 Version
Note : run an extra "reset master" step as part of the process on the slave (once more) after running the create_slave.sh and cloning the ssg db