| Bug #80446 | mysqlfailover process crash with mysql 5.7 simple failover | ||
|---|---|---|---|
| Submitted: | 19 Feb 2016 16:11 | Modified: | 14 Aug 2016 14:40 |
| Reporter: | Nicolas Moreau | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Utilities | Severity: | S1 (Critical) |
| Version: | 1.5.6 | OS: | Red Hat (7.1) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | failover;mysqlfailover | ||
[23 Feb 2016 8:15]
Nicolas Moreau
this in in line 1428 I have checked in version 1.6, this is the same case (not tested but the "global" keyword is missing at the same line).
[14 Jul 2016 14:40]
Chuck Bell
This was fixed in release-1.6.3. Please test with that version to confirm your issue is solved.
[15 Aug 2016 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: I was testing mysqlfailover with semi sync plugin with mysql 5.7.10 on redhat system. A simple test with one master and one slave replication was running, but when I stopped the master to test election (with a systemctl stop mysqld) in automatic mode (not in daemon), mysqlfailover process crashed with this error : Failed to reconnect to the master after 3 attemps. Failover starting in 'auto' mode... 2016-02-19 16:55:41 PM CRITICAL The server 10.32.1.28:3306 does not comply to the latest GTID feature support. Errors: Missing gtid_executed system variable. ERROR: The server 10.32.1.28:3306 does not comply to the latest GTID feature support. Errors: Missing gtid_executed system variable. We want to use it on production but with this bug it is not safe for now, the failover is not working and so the mysql service is not guaranted How to repeat: two mysql 5.7.10 with semi sync plugin installed and enabled, on redhat 7.1, mysqlfailover process on master (only for testing) no specific option only all necessaries for this. On internet someone says it is only because mysqlfailover launch : "SHOW VARIABLES LIKE 'gtid_executed'" wich return nothing instead off "SHOW GLOBAL VARIABLES LIKE 'gtid_executed'" Suggested fix: maybe from this file : mysql/utilities/common/server.py I have not edited it but i think i will but i dont know how to publish it