Bug #53530 Wrong status (ACTIVE BINLOG) in the BINARY LOG after a crash

• Submitted: 10 May 2010 8:03
• Modified: 18 Mar 2011 15:29
• Reporter: Alfranio Tavares Correia Junior
• Status: Closed
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 5.0, 5.1, 5.5
• OS: Any
• Assigned to: Daogang Qu
• CPU Architecture: Any
• Tags: binary log, crash, recovery

[10 May 2010 8:03] Alfranio Tavares Correia Junior

Description:
When a server shuts down, the binary log is properly closed and the LOG_EVENT_BINLOG_IN_USE_F in the header is cleared. However, when the
server crashes the flag is not cleared. 

So, the newer and prior binary logs have the same header information.

How to repeat:
Check the code.

Suggested fix:
After startup, fix the status of the latest binary log file.

[12 May 2010 3:37] Zhenxing He

I think this flag actually means that the binlog file is either in use or not properly closed (the name of the flag is kind of misleading), so I think the flags should not be automatically cleared after restart of the server.

[18 Mar 2011 15:29] Jon Stephens

Fixed as part of WL#5493. Closed.