Timeline for Accidentally executed reset master on the live server
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 26, 2016 at 11:34 | comment | added | rewb0rn | makes sense, thank you. restoring from scratch now, just to be sure. | |
| Jan 26, 2016 at 11:08 | vote | accept | rewb0rn | ||
| Jan 26, 2016 at 9:03 | comment | added | mysql_user | it is possible that your reset master have erased the data before it got replicated... check for error log for more information about last binary log co-ordinates and match it with slaves... if not... Restoring slave is a sure shot here but if not possible or if data's too large you may checksum/sync your data. | |
| Jan 26, 2016 at 8:57 | comment | added | rewb0rn |
Thanks, is there a way to find out if they were in sync? Considering this is a live environment with hundreds of requests per minute, there might be a chance that a transaction has been executed just before I called RESET MASTER and before the slaves could read it, right?
|
|
| Jan 26, 2016 at 7:56 | history | answered | mysql_user | CC BY-SA 3.0 |