Comments on: Galera Error Failed to Report Last Committed (Interrupted System Call)

By: Krunal Bauskar

Krunal Bauskar — Tue, 20 Feb 2018 03:00:24 +0000

In reply to Vasiliy Petrov. This simply means that the said node was unable to send the commit report notification to group channel probably due to heavy n/w traffic. It is again from same category and can be ignored but it also signals an important warning that you probably want to re-evaluate your load and available n/w bandwidth. Not that things will break immediately but if things keeps growing in this way you may see node dropping in future due to n/w issues.

By: Vasiliy Petrov

Vasiliy Petrov — Tue, 06 Feb 2018 06:24:00 +0000

I had little different message
[Warning] WSREP: Failed to report last committed 285293519, -110 (Connection timed out)
What does it mean?

By: Roel Van de Paar

Roel Van de Paar — Tue, 09 Aug 2016 10:01:46 +0000

On PXC 5.7, using local sysbench, I see this message on a HDD:

2016-08-09T09:43:58.131621Z 0 [Warning] WSREP: Failed to report last committed 71, -4 (Interrupted system call)
2016-08-09T09:44:01.746062Z 0 [Warning] WSREP: Failed to report last committed 43, -4 (Interrupted system call)
2016-08-09T09:44:04.974485Z 0 [Warning] WSREP: Failed to report last committed 45, -4 (Interrupted system call)
2016-08-09T09:44:12.695912Z 0 [Warning] WSREP: Failed to report last committed 51, -4 (Interrupted system call)
2016-08-09T09:44:16.046751Z 0 [Warning] WSREP: Failed to report last committed 53, -4 (Interrupted system call)

The same does not happen on a SSD in the same server (otherwise all remaining equal)