Bug #33864 shutting down a slave while 'stop slave' is running causes a crash

Submitted:	14 Jan 2008 15:04	Modified:	20 Jul 2009 22:30
Reporter:	Shane Bester (Platinum Quality Contributor)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.0.54-enterprise	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	slave_shutdown

Description:
While trying to repeat bug #31190 , I found the following problem:
I had left a script running to start and stop replication continuously.
Then, when issuing mysqladmin -uroot shutdown, the mysqld process segfaulted.

ntdll.dll!RtlEnterCriticalSection
mysqld-nt.exe!lock_slave_threads
mysqld-nt.exe!stop_slave
mysqld-nt.exe!mysql_execute_command
mysqld-nt.exe!mysql_parse
mysqld-nt.exe!dispatch_command
mysqld-nt.exe!do_command
mysqld-nt.exe!handle_one_connection
mysqld-nt.exe!pthread_start
mysqld-nt.exe!_threadstart
kernel32.dll!FlsSetValue

How to repeat:
setup replication.
in a loop, run 'start slave' then 'stop slave'.
then in another console, mysqladmin -uroot shutdown.

I think this is related to bug #26000

Many thanks for writing a bug report.

Please try actual bzr (5.1 (5.0)) tree here and let us know if this error still occurs.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

See also bug #44467

Race condition involving the server shutdown thread and a slave thread
is handled by  Bug#38694 (5.0) and earlier by Bug#29968 (5.1, not
back-ported that time).

Set back to verified because feedback was given.

Page generated in 0.060 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.