MySQL Bugs: #80342: session_track

Bug #80342	session_track_gtids is not optimal
Submitted:	11 Feb 2016 15:04	Modified:	11 Feb 2016 15:42
Reporter:	Mikiya Okuno	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.7.11	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Currently, session_track_gtids system variable may have either of following values:

* OFF
* OWN_GTID
* ALL_GTIDS

The reference manual states about OWN_GTID as follows: OWN_GTID configures the tracker to collect GTIDs generated by successfully committed read/write transactions.

This is untrue. OWN_GTID reflects simply gtid_owned. So, GTID is included in OK packet only when gtid_next is set beforehand. This is not useful.

How to repeat:
See attachment.

Suggested fix:
Change the behavior of session_track_gtids according to the manual. I suggest to have an additional member to hold the last gtid in THD class, or change the meanings of THD::owned_gtid and hold the last gtid in it.

Ugly ugly test program. Modify credentials according to your environment.

Attachment: gtid-test.c (text/x-csrc), 3.84 KiB.

You need following server options to run this program:

log_bin=mysql-bin
server_id=1
gtid_mode=on
enforce_gtid_consistency=on
session_track_gtids=OWN_GTID

The test program can return GTID in the OK packet, actually. Because it issues a "SET GTID_NEXT" command beforehand. IMHO, "SET GTID_NEXT" should be unnecessary.

Test program without SET GTID_NEXT

Attachment: gtid-test-rev2.c (text/x-csrc), 2.48 KiB.

I'm sorry. I made a mistake in sequence of calling API functions. This is not a bug. Please close.