Bug #75285 Improve documentation of expected logging when recovery takes place
Submitted: 22 Dec 2014 11:37 Modified: 12 Apr 2017 16:06
Reporter: Simon Mudd (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S4 (Feature request)
Version:5.7.5 OS:Any
Assigned to: CPU Architecture:Any
Tags: innodb recovery, logging

[22 Dec 2014 11:37] Simon Mudd
Description:
http://dev.mysql.com/doc/refman/5.7/en/innodb-recovery.html describes the process but there's no sample logging of what you expect to see.
Given this happens when there's a crash and something bad has happened it's handy when you look at the documentation if there are some examples of what you might expect to see in these circumstances.
This way you can confirm you see what you expect at each stage of the recovery process.

How to repeat:
look at the docs and see the process is described but no logging is shown.

Suggested fix:
I think it might be handy to have some example snippets of the logging when recovery is taking place so you can see what would be logged.

The same issue is true of MySQL 5.6 and earlier but given the logging changes quite a bit in 5.7 it's probably only worth fixing the documentation for 5.7.
[8 Dec 2016 8:30] Jon Stephens
Updated wrong category so this can be assigned to right Docs writer for resolution.

This was my mistake, so please accept my apologies for the unnecessary delay.
[12 Apr 2017 16:06] Daniel Price
Posted by developer:
 
A logging output example was added to the InnoDB crash recovery documentation.
https://dev.mysql.com/doc/refman/5.7/en/innodb-recovery.html#innodb-crash-recovery

Thanks for the bug report.