Timeline for MYSQL cluster issue: shutdown data node correctly breaks replication
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2021 at 22:58 | comment | added | Mikael Ronström | Hard to say for certain without more logs and so forth. But 4009 means that the MySQL Server has lost contact with ALL data nodes. This can happen even if some data nodes are still up since each MySQL Server has a separate connection to each data node that is using heartbeats, so a general overload could cause or that the MySQL Server VM is not communicating for a while, look into the cluster log might provide more details. | |
| Mar 1, 2021 at 14:33 | comment | added | gojo | Hello Mikael, thanks for this feedback we have 4 datanodes (for redondancy) in the cluster and i only powered off single one, the other one were up and running, just trying to underdand why replication went to down in this case | |
| Mar 1, 2021 at 10:23 | history | answered | Mikael Ronström | CC BY-SA 4.0 |