[MDEV-23682] A node becomes inconsistent (WSREP_LOCAL_STATE = 5) Created: 2020-09-07  Updated: 2022-02-07  Resolved: 2022-02-07

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.4.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Levieux stéphane Assignee: Ramesh Sivaraman
Resolution: Incomplete Votes: 3
Labels: None

Attachments: File node1.err    

 Description   

Sometimes (once a week), a node of our Galera Cluster ( 3 nodes) reaches an inconsistent state (WSREP_LOCAL_STATE = 5)

The cluster continues to work on the 2 others nodes.

In the log, I noticed these messages each time the problem occurs:

2020-09-05  0:06:56 240929 [Warning] WSREP: TO isolation failed for: 1, schema: information_schema, sql: FLUSH STATUS. Check wsrep connection state and retry the query.
2020-09-05  0:16:57 240929 [Warning] WSREP: TO isolation failed for: 1, schema: information_schema, sql: FLUSH STATUS. Check wsrep connection state and retry the query.
2020-09-05  0:26:57 240929 [Warning] WSREP: TO isolation failed for: 1, schema: information_schema, sql: FLUSH STATUS. Check wsrep connection state and retry the query.
2020-09-05  0:36:57 240929 [Warning] WSREP: TO isolation failed for: 1, schema: information_schema, sql: FLUSH STATUS. Check wsrep connection state and retry the query.
.....



 Comments   
Comment by Jan Lindström (Inactive) [ 2021-09-23 ]

I do not follow, PR has been merged to 10.4 and after that it should be merged upwards to 10.5. From there it should be rebased on 10.5 ES. All this is normal procedure and based on code review PR is there. So, if there is a issue it must be something new or there is bug on PR.

Comment by Jan Lindström (Inactive) [ 2021-09-28 ]

Based on commits, this issue has been fixed on 10.4-10.6.

Generated at Thu Feb 08 09:24:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.