Bug #50910 confusing docs lines about replication group termination wth stop slave

Submitted:	4 Feb 2010 12:05	Modified:	4 Feb 2010 16:10
Reporter:	Andrei Elkin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1+	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any
Tags:	"replication group termination"

Description:
The lines of 5.1 docs should be corrected

  12.6.2.8 `STOP SLAVE' Syntax

  The transactional behavior of *note `STOP SLAVE': stop-slave. changed
  in MySQL 5.1.35. Previously, it took effect immediately; beginning with
  MySQL 5.1.35, it waits until the current replication event group (if any) has  finished executing

in that actually

the slave  waits until the current repl group has finished if a non-trans table was modified.

How to repeat:
To look at the docs.

Suggested fix:
To consider 

  slave waits until the current replication event group (if any)
  has finished executing if it modified a non-transactional table,
  or until...

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.