Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

A lot of WSREP: Failed to report last committed <number>, -110 (Connection timed out)

Description

I'm using  Percona-XtraDB-Cluster-server-56 with Version : 5.6.39 Release : 26.25.1.el6.

with 2 node + 1 percona-xtradb-cluster-garbd.

I'm facing following problem. PXC log report a a lot of warning 

 

It make any SQL transaction like insert and update in commit stage very slow, usual take 10-11 sec to finish. Normaly that sql only take less then 1 second.

The ping between 2 node PXC is less than 0.2ms, and no drop package.

Following is my.conf. similar on 2 node.

 

 

 

 

 

 

 

Environment

None

Attachments

1

Smart Checklist

Activity

Show:

Aaditya Dubey April 13, 2022 at 11:32 AM
Edited

Hi ,

Thank you for the report.
This simply means that the said node was unable to send the commit report notification to group channel probably due to heavy network traffic. It can be ignored but it also signals an important warning that you probably want to re-evaluate your load and available network bandwidth.

Please note that 5.6 reached to end of life, please upgrade to latest version of .7, if you still see the issue please update the bug report.

please visit this reference document for product life cycle:https://www.percona.com/services/policies/percona-software-support-lifecycle#mysql

Please go through the document for more details about the warning https://www.percona.com/blog/2016/05/27/galera-error-failed-to-report-last-committed-interrupted-system-call/

lihomehuang February 24, 2022 at 8:04 AM

did you fix the problem? I get the same troubles.

Yuriy December 29, 2021 at 10:04 AM

Same problem here. Detected in large amount of INSERT's or UPDATE's

Done

Details

Assignee

Reporter

Labels

Affects versions

Priority

Smart Checklist

Created December 29, 2021 at 10:03 AM
Updated March 6, 2024 at 9:00 PM
Resolved April 13, 2022 at 11:32 AM
Configure