Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-17550

Improve WSREP's "Failed to report last committed" warning message

Details

    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?

      Attachments

        Issue Links

          Activity

            GeoffMontee Geoff Montee (Inactive) added a comment - 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/

            People

              teemu.ollakka Teemu Ollakka
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.