Bug #20856 Aborting a statement should not cause error 1053 (Server shutdown)
Submitted: 4 Jul 2006 22:53 Modified: 4 Oct 2008 22:57
Reporter: Daniel Schneller Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Errors Severity:S4 (Feature request)
Version:4.1.12 OS:Windows (Windows)
Assigned to: CPU Architecture:Any

[4 Jul 2006 22:53] Daniel Schneller 
Description:
Connecting to a MySQL server from two clients (A and B) and killing a statement client A started from client B, will cause client A to abort with error code 1053 (server shutdown).
This makes it hard to react appropriately from an application point of view. Moreover this will break replication, because the error code is sent to the slave along with the statement. When the statement executes on the slave, it will have an error code of 0. When error codes differ, the replication stops.

How to repeat:
See description

Suggested fix:
Have separate error codes for aborted statements and a real server shutdown. This allows client programs to react appropriately and replication can be set to ignore this if desired.
[8 Jul 2006 9:16] Valeriy Kravchuk 
Thank you for a reasonable feature request.
[4 Oct 2008 22:57] Konstantin Osipov 
This is a duplicate of Bug#18256 Kill thread -> error: server shutdown