pt-slave-restart fails on MariaDB 10.0.13 (gtid_mode confusion)
Bug #1362942 reported by
Simon J Mudd
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Fix Released
|
Medium
|
Frank Cizmich |
Bug Description
[root@myhost ~]# pt-slave-restart --error-
DBD::mysql::db selectrow_arrayref failed: Unknown system variable 'gtid_mode' [for Statement "SELECT @@GLOBAL.
[root@myhost ~]# rpm -q percona-toolkit
percona-
[root@myhost ~]# rpm -q MariaDB-server
MariaDB-
[root@myhost ~]# rpm -q centos-release
centos-
[root@myhost ~]#
This seems to work fine for MariaDB 5.5, MySQL 5.5 and I think also for MySQL 5.6.
I've not investigated further but MariaDB 10 is the latest GA version so I think this command would be expected to work.
Changed in percona-toolkit: | |
status: | Fix Committed → Fix Released |
Changed in percona-toolkit: | |
milestone: | 2.2.17 → 2.2.20 |
To post a comment you must log in.
This is easy to confirm with code review:
... SKIP_COUNTER >new($dbh) >= '5.6.5' ) { _arrayref( 'SELECT @@GLOBAL. gtid_mode' ); gtid_mode: ', $row->[0]);
4991 # When MySQL 5.6.5 or higher is used and gtid is enabled, skipping a
4992 # transaction is not possible with SQL_SLAVE_
4993 my $skip_event;
4994 my $have_gtid = 0;
4995 if ( VersionParser-
4996 my $row = $dbh->selectrow
4997 PTDEBUG && _d('@@GLOBAL.
4998 if ( $row && $row->[0] eq 'ON' ) {
4999 $have_gtid = 1;
5000 }
5001 }
5002 PTDEBUG && _d('Have GTID:', $have_gtid);
...
So, there is no special handling for MariaDB - only version matters.