Replication fails and the node becomes Inconsistent if transaction is committed on node by setting tagged gtid
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:

Venkatesh Prasad December 31, 2024 at 12:23 PMEdited
It hits a debug assertion in 8.4 branch
Details
Details
Assignee

Reporter

Labels
Planned Version/s
Needs QA
Yes
Sprint
Affects versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created October 22, 2024 at 4:45 PM
Updated March 2, 2025 at 8:00 PM
Setup 3 nodes PXC cluster (release-8.4.0 branch)
Create database say 'test' and create table say test.t by connecting to node1. ie,
mysql> create database test;
mysql> create table test.t(a int primary key);
Connect to node1 and execute some insert by setting a tagged gtid ie,
mysql> set @@session.GTID_NEXT='1ed6b5f2-9091-11ef-b382-13ba123de7b3:abc124:1';
mysql> insert into test.t values(214);
The other two nodes errors out while applying the write-set as it hits the errors while reading event (wsrep_read_log_event). seems due to the tagged gtid.
Since node2 and node3 will have same state hence they both form a group and node1 is marked as inconsistent.
Node2 error log: