Actually, Galera, atleast now, supports wsrep replication position in InnoDB headers, much like how the replication position is stored and recovered during prepare phase of Xtrabackup.
According to discussion I had, it stored as follows:
""
Wsrep GTID is found from InnoDB sys_header + TRX_SYS_WSREP_XID_INFO, see:
* storage/innobase/include/trx0sys.h for TRX_SYS_WSREP_XID_INFO and other definitions
* storage/innobase/trx/trx0sys.c:trx_sys_read_wsrep_checkpoint() for reading XID from sys_header
* sql/wsrep_mysqld.h and sql/wsrep_utils.cc how to read GTID from XID (wsrep_xid_{uuid|seqno})
* XID is defined in sql/handler.h and storage/innobase/include/trx0xa.h
""
May be a different bug can be opened for this if required.
Actually, Galera, atleast now, supports wsrep replication position in InnoDB headers, much like how the replication position is stored and recovered during prepare phase of Xtrabackup.
According to discussion I had, it stored as follows:
"" WSREP_XID_ INFO, see: innobase/ include/ trx0sys. h for TRX_SYS_ WSREP_XID_ INFO and other definitions innobase/ trx/trx0sys. c:trx_sys_ read_wsrep_ checkpoint( ) for reading XID from sys_header xid_{uuid| seqno}) innobase/ include/ trx0xa. h
Wsrep GTID is found from InnoDB sys_header + TRX_SYS_
* storage/
* storage/
* sql/wsrep_mysqld.h and sql/wsrep_utils.cc how to read GTID from XID (wsrep_
* XID is defined in sql/handler.h and storage/
""
May be a different bug can be opened for this if required.