[MDEV-26359] WSREP_LAST_WRITTEN_GTID returns incorrect result Created: 2021-08-13  Updated: 2023-02-01

Status: Open
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.5.12
Fix Version/s: 10.5

Type: Bug Priority: Major
Reporter: Steve Hunger Assignee: Seppo Jaakola
Resolution: Unresolved Votes: 0
Labels: None
Environment:

Galera cluster consisting of 3 nodes running MariaDB 10.5.12 on Debian Buster



 Description   

Querying "SELECT WSREP_LAST_WRITTEN_GTID()" at the same time with different connections on one single node yields different results.

The GTIDs returned are way of from each other:
Connection 1: 0-1-3311413119
Connection 2: 0-1-3311399223
Connection 3: 0-1-3311430041
Connection 4: 0-1-3311374352

Lowest GTID returned was from about 10 minutes before.

Even 15 minutes later WSREP_LAST_WRITTEN_GTID returned the GTID 0-1-3311401500 on a fresh new connection with one single write, which is still way lower then those from earlier.

To reproduce:
1. Create 2 or more connections
2. Run a simple write query
3. SELECT WSREP_LAST_WRITTEN_GTID()
4. Compare the results

Expected behaviour should be a steady increasing GTID.



 Comments   
Comment by Mario Karuza (Inactive) [ 2021-09-09 ]

Can you attach your configuration files for inspection.

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