Your message dated Sun, 3 Jul 2016 11:46:27 +0200
with message-id <[email protected]>
and subject line closing bugs reported against ancient mysql-5.1
has caused the Debian Bug report #698431,
regarding /usr/sbin/mysqld: replication freezes on INSERT IGNORE statement
since upgrade from 5.1.63 to 5.1.66 on a squeeze
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
698431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698431
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server-core-5.1
Version: 5.1.66-0+squeeze1
File: /usr/sbin/mysqld
Severity: important
*** Please type your report below this line ***
Since last upgrade from 5.1.63 to 5.1.66, after a while, replication on
the slave begins drifting relative to the master position.
A "show processlist" indicates that slave is stuck on an "INSERT IGNORE"
statement. And from that point, replication is frozen and "seconds
behind master" starts to increase more and more.
Here is the output from a "show processlist" on the slave :
*************************** 1. row ***************************
Id: 1
User: system user
Host:
db: NULL
Command: Connect
Time: 60497
State: Waiting for master to send event
Info: NULL
*************************** 2. row ***************************
Id: 2
User: system user
Host:
db: referential
Command: Connect
Time: 36978
State: Sending data
Info: INSERT IGNORE INTO symfony.ebook_author (ebook_id,author_id)
(
SELECT ec.ebook_id as ebook_id, a
*************************** 3. row ***************************
Id: 1536
User: debian-sys-maint
Host: localhost
db: NULL
Command: Query
Time: 0
State: NULL
Info: show processlist
And at the same time, "Seconds_Behind_Master" is 36968.
I tried a rollback to 5.1.63 for the following packages :
libmysqlclient16
mysql-client-5.1
mysql-common
mysql-server-5.1
mysql-server
mysql-server-core-5.1
Replication then just works fine, for as long as I let it run (almost 3
days). Seconds behind master remained all that time 0s.
If I upgrade slave again to last version 5.1.66, even with replication
restarted from scratch on the slave, bug is reproduced (the output
pasted above is from this second try)
Master version is 5.1.66 too.
To reproduce, i guess you can configure a master/slave replication with
5.1.66 on Debian Squeeze servers and try to execute an INSERT IGNORE on
the master which should then freeze replication process on the slave.
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mysql-server-core-5.1 depends on:
ii libc6 2.11.3-4 Embedded GNU C Library:
Shared lib
ii libgcc1 1:4.4.5-8 GCC support library
ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3
ii libwrap0 7.6.q-19 Wietse Venema's TCP
wrappers libra
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
mysql-server-core-5.1 recommends no packages.
mysql-server-core-5.1 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of mysql (5.1),
that was last released with Debian 6.0 (squeeze). But even squeeze-lts
has now reached end-of-life and is no longer supported.
The bug is assumed to be fixed (or no longer relevant) in newer mysql
(or mariadb) releases and therefore I'm closing this report now. If the
problem is still reproducible in the currently supported versions
(mysql-5.6/mysql-5.7), feel free to provide more information, reopen
and reassign this bug report.
Andreas
--- End Message ---
