MySQL Bugs: #93392: SHOW SLAVE STATUS needs error GTID field

Bug #93392	SHOW SLAVE STATUS needs error GTID field
Submitted:	29 Nov 2018 0:30	Modified:	10 Aug 2023 14:49
Reporter:	Joe Vierra	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I am using multi master replication to synchronize 4 data centers around the world.    This feature is completely awesome!!!   Thanks for making this work!!!

However, it would be incredibly helpful if you could add a field to the output of "SHOW SLAVE STATUS" to show the error_GTID.    This field would be empty under normal conditions,   but would show the GTID of the transaction that is currently causing an error. 

Right now you show the error, but if you have multiple masters, it is not always obvious which master the error came from.    You need to know the master the error is coming from so you can skip over the correct GTID to get past the error.     Right now I have to guess which master has the error, and if I guess wrong, I am skipping a transaction I don't want to skip, so I am introducing replication errors on the slave, that if I knew the GTID of the transaction that was having the error, would be easy to avoid. 

How to repeat:
Run "SHOW SLAVE STATUS" when there is a replication error.

Suggested fix:
add a field to the output of "SHOW SLAVE STATUS" to show the "error_GTID"    This field would be empty under normal conditions,   but would show the GTID of the transaction that is currently causing an error.

Thank you for the request

Posted by developer:
 
Thanks for the suggestion. This information is already available in the performance_schema.replication_applier_status_by_worker table, column APPLYING_TRANSACTION, so no need to extend the SHOW statement.