MySQL patches by Codership

Avoid collisions on autoincrement values

Bug #320704 reported by Alex Yurchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Low
Seppo Jaakola
MySQL patches by Codership demo-2
wsrep API
Fix Released
Undecided
Unassigned

Bug Description

Currently all nodes increment AUTO_INCREMENT table values independently. This leads to high probability of certification collision on INSERT.

Nodes must be able to choose autoincrement values so that they don't collide (or collision probability is low)

Related branches

lp:codership-mysql/0.6
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

wsrep API version 2 offers cluster status callback, which can be used to re-configure auto_increment_increment and auto_increment_offset

Changed in codership-mysql:
assignee: nobody → seppo-jaakola
importance: Undecided → Low
status: New → In Progress
Revision history for this message
Seppo Jaakola (seppo-jaakola) wrote :

autoinc values don't propagate correctly in slave applying. This is native MySQL issue, and there is a bug report about it: http://bugs.mysql.com/bug.php?id=41986
...and a fix also: http://lists.mysql.com/commits/63196

I ported this fix to our 5.1.30 based wsrep intgeration.

Seppo Jaakola (seppo-jaakola)
Changed in codership-mysql:
status: In Progress → Fix Committed
Seppo Jaakola (seppo-jaakola)
Changed in codership-mysql:
milestone: none → demo-2
status: Fix Committed → Fix Released
Seppo Jaakola (seppo-jaakola)
Changed in wsrep:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.