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

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Galera, wsrep
    • Labels:
      None

      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

              People

              Assignee:
              ralf.gebhardt@mariadb.com Ralf Gebhardt
              Reporter:
              GeoffMontee Geoff Montee
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: