The current MYSQL master server has an outdated database.
Default Severity
Critical
Instance
N/A
HA Score
Degraded
Clearing Action
This alarm clears when the master server either is made a slave server or if a database restore action clears the condition.
OID
QPMySQLMasterOutdated
Recovery:
Once the condition has occurred, the 80003 event will be sent once a minute. Wait until all of the expected servers are being reported. It is important to wait because the best slave might be undergoing a restart and its DB Level will not be known until after the restart completes.
Use the information in 80003 to select the new master candidate.
Except for the current master and the master candidate, put all of the other servers into forced standby.
If the best secondary server is in the same cluster (the most common case), perform a failover by restarting the current active blade. If the best secondary server is in a separate cluster, then a site promotion is necessary.
Remove the forced standby settings on the other slaves.
If none of the slaves are good candidates, perform a database restore.
Put all of the slave servers into forced standby state.