MySQL Bugs: #37926: server option to restart binary log data in the event of an error

Bug #37926	server option to restart binary log data in the event of an error
Submitted:	7 Jul 2008 13:14
Reporter:	Matthew Lord	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S4 (Feature request)
Version:		OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
In the event of a power failure or other improper shutdown of a machine you
may encounter one of these failures with opening the binary log related files:
1. binlog has bad magic number. Its not a binary log file that can be used by this version of mysql
2. can’t init tc log

We should add a server option that tells mysqld to force a reload of the binary
log related files so that it may continue starting up.

How to repeat:
N/A

Suggested fix:

We should add a server option that tells mysqld to force a reload of the binary
log related files so that it may continue starting up such as:
--force-binary-log-reload-on-error