Bug #83299 | 5.7 broke replica - Could not find first log file name in binary log index file | ||
---|---|---|---|
Submitted: | 7 Oct 2016 10:14 | Modified: | 11 Nov 2016 9:04 |
Reporter: | Steven Hartland | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7.15 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[7 Oct 2016 10:14]
Steven Hartland
[10 Oct 2016 9:55]
MySQL Verification Team
Hello Steven, Thank you for the report. Could you please tell us whether you've upgraded slave, master first? Also, please could you upload both the conf files, unaltered error logs from master/slave to check further? In general, when you upgrade a master to 5.7 from an earlier MySQL release series, you should first ensure that all the slaves of this master are using the same 5.7.x release. If this is not the case, you should first upgrade the slaves. Thanks, Umesh
[11 Nov 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".
[11 Nov 2016 9:04]
Steven Hartland
Sorry never got the email to say there was a question waiting. Yes the slave was upgraded prior to the slave, however the cause of the issue was actually a bug in the FreeBSD port / package which documented the move of the configuration file incorrectly so it wasn't using the my.cnf everyone thought it was. This resulted in the changes in format of mysql-bin.index and hence the temporary failure of the replication.