pt-slave-restart doesn't print GTID of skipped transaction

Bug #1325839 reported by Stéphane Combaudon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Confirmed
Undecided
Unassigned

Bug Description

How to reproduce:

1) Set up a master and slave with GTID-based replication.
2) Create a replication error on the slave.
3) Run pt-slave-restart to skip the offending transaction on the slave.

The output looks like:
# pt-slave-restart h=127.0.0.1,u=root,P=13002
2014-06-03T09:22:25 P=13002,h=127.0.0.1,u=root wheezy-relay-bin.000002 361 1062

Having the binlog file and position of the offending transaction is fine, having the GTID of that transaction is also useful.

Revision history for this message
Stéphane Combaudon (stephane-combaudon) wrote :

Forgot to mention this is with pt-slave-restart 2.2.8

tags: added: pt-slave-restart
Revision history for this message
Nilnandan Joshi (nilnandan-joshi) wrote :

Verified with pt-slave-restart 2.2.10. GTID of that transaction doesn't print.

nilnandan@nilnandan-Dell-XPS:~$ pt-slave-restart --version
pt-slave-restart 2.2.10
nilnandan@nilnandan-Dell-XPS:~$
nilnandan@nilnandan-Dell-XPS:~$ pt-slave-restart h=127.0.0.1,u=root,p=msandbox,P=19681
2014-08-13T14:51:31 P=19681,h=127.0.0.1,p=...,u=root mysql_sandbox19681-relay-bin.000002 631 1008
^CExiting on SIGINT.
nilnandan@nilnandan-Dell-XPS:~$

Changed in percona-toolkit:
status: New → Confirmed
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1227

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.