# Innodb deadlock bug in v5.5.29

**URL:** https://forums.percona.com/t/innodb-deadlock-bug-in-v5-5-29/2006
**Category:** Other MySQL® Questions
**Created:** [March 4, 2013, 7:46pm UTC](https://forums.percona.com/t/innodb-deadlock-bug-in-v5-5-29/2006 "2013-03-04T19:46:40Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![rveloso](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@rveloso](https://forums.percona.com/u/rveloso)
#### Post date: [March 4, 2013, 7:46pm UTC](https://forums.percona.com/t/innodb-deadlock-bug-in-v5-5-29/2006/1 "2013-03-04T19:46:40Z")

</div>

Can you guys please confirm this is fixed in percona server 5.5.29-30.0-log?

[bugs.mysql.com/bug.php?id=52020](http://bugs.mysql.com/bug.php?id=52020)

Im having innodb deadlocks left and right using insert on duplicate key update…

---

<div class="post-metadata">

### Author: ![niljoshi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/niljoshi/32/16889_2.png) [@niljoshi](https://forums.percona.com/u/niljoshi)
#### Post date: [March 6, 2013, 2:29am UTC](https://forums.percona.com/t/innodb-deadlock-bug-in-v5-5-29/2006/2 "2013-03-06T02:29:51Z")

</div>

Hi,

52020 is fixed in MySQL as per last comment in ([MySQL Bugs: #52020: InnoDB can still deadlock on just INSERT...ON DUPLICATE KEY](http://bugs.mysql.com/bug.php?id=52020)) so it will be definitely fixed in Percona Server. But there is also one more 50413, which is not fixed yet.

---

<div class="post-metadata">

### Author: ![rveloso](https://avatars.discourse-cdn.com/v4/letter/r/a8b319/32.png) [@rveloso](https://forums.percona.com/u/rveloso)
#### Post date: [March 6, 2013, 3:31am UTC](https://forums.percona.com/t/innodb-deadlock-bug-in-v5-5-29/2006/3 "2013-03-06T03:31:31Z")

</div>

see my comments there, that bug is not fixed as is fairly easy to replicate. i can show you some traces if needed. Are you guys gonna get ahead of mysql and fix it? 😉