[MDEV-17550] Improve WSREP's "Failed to report last committed" warning message Created: 2018-10-25  Updated: 2023-12-19

Status: Open
Project: MariaDB Server
Component/s: Galera, wsrep
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Teemu Ollakka
Resolution: Unresolved Votes: 4
Labels: None

Issue Links:
Relates
relates to MDEV-19743 Crash while reorganizing an index page Closed
relates to MDEV-15261 WSREP: Failed to report last committed Closed

 Description   

When a Galera Cluster is under a lot of load, it's common for the log to have warning messages like:

[Warning] WSREP: Failed to report last committed 211651504, -4 (Interrupted system call)

or

[Warning] WSREP: Failed to report last committed 342386158, -110 (Connection timed out)

"Failed to report last committed" sounds like a serious problem, but I've been told that these warnings don't necessarily mean that anything has gone wrong. It usually just means that the cluster is under a lot of load.

Can we improve this warning, so that the meaning is easier for users and DBAs to understand?

 Comments   
Comment by Geoff Montee (Inactive) [ 2019-11-01 ]

See this blog post by manjot for some more information about these messages:

https://www.percona.com/blog/2016/05/27/galera-error-failed-to-report-last-committed-interrupted-system-call/

Generated at Thu Feb 08 08:37:19 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.