HiveBrain v1.2.0
Get Started
← Back to all entries
patternMinor

WSREP: failed to report last committed and stop

Submitted by: @import:stackexchange-dba··
0
Viewed 0 times
lastcommittedstopreportfailedwsrepand

Problem

I have galera cluster and I have 4 nodes. I'm importing some data. however one node gives error. Warning. The warning is;

warning WSREP: Failed to report last committed 59102, -q (interrupted system call) 
mysqld_safe Number of processes running now: 0
mysqld_safe WSREP: not restarting wsrep node automatically
mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended


What is that error? How can I solve this? This node shouldn't stop, not mysql service stopped in that error. Thanks

Solution

warning WSREP: Failed to report last committed

This is just a warning, and in itself isn't a cause for concern. I think it's unlikely that this caused the node to stop. See also Percona's blog post about it.

And then:


mysqld_safe Number of processes running now: 0

Again, according to Percona (Support):


Your mysqld process was killed, most likely by OOMkiller. Check the system log. Joining node will refuse to accept connections until it synchronizes with cluster.

Context

StackExchange Database Administrators Q#119753, answer score: 2

Revisions (0)

No revisions yet.