We received the below error on our production server, which caused the database server to crash. Despite being a 3 node cluster, we direct all read and write operations to one node, using the other 2 nodes as hot spares. Upon failure, all access redirected to one of the other nodes in the cluster with no issue.
I have attached the syslog containing all the events that occured afterwards in case they are useful. Of note, it appears that the first restart of the server, had trouble synchronising because of an unexpected primary key. I suspect our on-call engineers then deleted the DB, forcing an SST. I have trimmed the log where it is copying and moving several files.