Public bug reported:

Copied from debian bug report with slight changes.

Hi,

I am recently upgrading one of the slaves of a master-slave replication
to feisty, for 2 reasons:

1. attempt to fix http://bugs.mysql.com/bug.php?id=20188 which claims to
be fixed since 5.0.24

2. rehearse the migration; since we can afford zero downtime, we
can only first migrate slave to new version, switch it to a master, and
then upgrade the original master with a reversed replication

Then I begin to be hit by http://bugs.mysql.com/bug.php?id=24432 .
To repeat the details in the 2 bug reports, the fix of 20188 has
introduced another bug which make any version newer than 5.0.24 give a
wrong auto_increment behavior (irrespective to replication). This
behavior is finally fixed by 24432 in the recent 5.0.38 version.
The wrong auto_increment behavior in its own is a bit mild (it skips
some usable auto_increment values) but it causes replication problems
with other master/slave without this bug.

This bug is serious because any of the master or the slave with version
between 5.0.24 and 5.0.36 inclusive will make replication fail, although
it will work if both master and slave are within this range of versions.
See the chart in the bug report for more details.

If feisty ships with an unpatched version of 5.0.32, then people will have
a hard time upgrading to feisty, and also upgrading to feisty+1 later.
Since the bug is only fixed in upstream in 5.0.38, which is very
unlikely to be uploaded to feisty, I propose to backport the patch.

Here is the patch: http://lists.mysql.com/commits/19547

Backporting the patch will be a bit tricky, since upstream has inserted
some code to detect version numbers to determine whether a certain
replication will fail or survive. If ubuntu make their 5.0.32-10ubuntu1
free of this bug, then the logic there has to be altered.

Maybe it is safe for us to drop the checking, but this may cause problem
if some people run a replication between ubuntu and another distro.

-- 
Regards,
Alan

** Affects: mysql-dfsg-5.0 (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed
** Affects: mysql-dfsg-5.0 (Debian)
     Importance: Unknown
         Status: Unknown

** Bug watch added: Debian Bug tracker #416145
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416145

** Also affects: mysql-dfsg-5.0 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416145
   Importance: Unknown
       Status: Unknown

-- 
Replication failure with auto-increment and on duplicate key update
https://launchpad.net/bugs/95821

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to