[MDEV-16204] Data inconsistency is observed on the cluster after waiting for table metadata lock occurred on Galera Node Created: 2018-05-17 Updated: 2023-06-06 Resolved: 2023-06-06 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 10.3.6 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Zdravelina Sokolovska (Inactive) | Assignee: | Seppo Jaakola |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Environment: |
Galera Master-Master 2 Nodes ;CentOS 7.4. |
||
| Issue Links: |
|
||||||||
| Description |
|
Data inconsistency is observed on the cluster after waiting for table metadata lock occurred on Galera Node the wsrep status does not show any indication about the occurred inconsistency , On Node 1 occurred waiting for table metadata lock Below on Node1 table CUSTOMER returns results while on Node2 Node2
Node1
\
It appears consecutively that Node1 hangs on 'drop' and 'create' statements
|
| Comments |
| Comment by Zdravelina Sokolovska (Inactive) [ 2018-05-22 ] |
|
At least wsrep status should notify about the occurred inconsistency in the cluster . |
| Comment by Zdravelina Sokolovska (Inactive) [ 2018-05-22 ] |
|
Galera Cluster v4 may avoid such data inconsistency via the intended inconsistency voting protocol in galera4 ? |
| Comment by Jan Lindström [ 2023-06-06 ] |
|
10.3 is EOL soon. |