Bug #90997 "Handling an Unexpected Halt of a Replication Slave" manual page is wrong

• Submitted: 23 May 2018 16:57
• Modified: 20 Oct 2020 10:58
• Reporter: Sveta Smirnova (OCA)
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 5.7.22
• OS: Any
• CPU Architecture: Any

[23 May 2018 16:57] Sveta Smirnova

Description:
Documentation at https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-unexpected-slave-halt.html says what recovery is guaranteed after any crash if slave uses GTIDs and MASTER_AUTO_POSITION. However this is not true if sync_binlog != 1 and innodb_flush_log_at_trx_commit != 1 as reported in bug #70659

How to repeat:
Repeat instructions in bug #70659

Suggested fix:
Fix bug #70659 or update documentation.

[28 May 2018 16:28] MySQL Verification Team

Thanks for the report Sveta

all best
Bogdan

p.s. verified of course

[21 Aug 2018 17:55] Jean-François Gagné

Related with a suggested fix: Bug#92109.

[20 Oct 2020 10:58] Margaret Fisher

Posted by developer:
 
Thanks to all those who raised and contributed to discussions of this issue. The "Handling an Unexpected Halt of a Replica" topic has now been reworked in the 8.0 and 5.7 documentation to focus on a recommended combination of server settings for recovery, rather than addressing all the possible combinations. Please see the updated topics here:

https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-unexpected-replica-halt.html
https://dev.mysql.com/doc/refman/5.7/en/replication-solutions-unexpected-replica-halt.html