[MDEV-11394] AliSQL: [Feature] Issue#16 OMIT MAINTAINING OWNED_GTID SET IF GTID IS AUTO-GENERATED Created: 2016-11-29  Updated: 2017-12-12  Resolved: 2017-11-17

Status: Closed
Project: MariaDB Server
Component/s: Replication
Fix Version/s: 10.3.2

Type: Task Priority: Major
Reporter: Sergey Vojtovich Assignee: Andrei Elkin
Resolution: Not a Bug Votes: 0
Labels: None

Epic Link: AliSQL patches
Sprint: 10.3.3-1

 Description   

Description:
------------
Before this patch, the life cycle for a GTID like the following:
Generate a GTID => Add the GTID into owned_gtid => Flush the GTID into binlog
=> Remove the GTID from owned_gtid. Owned_gtid can be treated as an intermediate
set to hold all of the GTIDs of current thread.
 
After this patch, the life cycle for such a GTID can be like this:
Generate a GTID => Add the GTID into binlog. Of course, if anything
wrong happens, we have to remove the GTID from the binlog. Before this
patch, we can remove the GTID from owned_gtid. Obviously, we shortened
the life cycle of GTID.
 
In order to support this feature, we introduced a new system variable
"rds_gtid_precommit". If it's on, we will change the life cycle of GTID.

https://github.com/alibaba/AliSQL/commit/aa5e331b00272e5b972a411d17f1079550eb04c1



 Comments   
Comment by Andrei Elkin [ 2017-11-17 ]

Unlike Mysql there is no notion of 'owned' gtid in Mariadb. Autogenerated gtid value
is always binlogged optimally not to hold any critical resource so there's nothing to
optimize.

Generated at Thu Feb 08 07:49:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.