pt-osc-handlehighconcurrentytable

Registered by Kenny Gryp on 2013-04-12

As discussed in percona customer ticket #29432:

- pt-osc does perform 'insert into ... select' statements, which is seen as a bulk insert statement and takes a AUTO-INC lock in autoincrement handling (http://dev.mysql.com/doc/refman/5.6/en/innodb-auto-increment-configurable.html only in 5.1 and up)
- there is a depth of 200 in innodb's internal deadlock mechanism (http://books.google.be/books?id=BL0NNoFPuAQC&pg=PA570&lpg=PA570&dq=waits+for+graph+200+innodb&source=bl&ots=COVOAuxH4U&sig=31Krn63eUnoeiSm8C_cP5hD2ack&hl=en&sa=X&ei=jc9nUaXFBYLK0AXGuoHwCw&ved=0CCwQ6AEwAA#v=onepage&q=waits%20for%20graph%20200%20innodb&f=false)

This is causing deadlocks to happen when pt-osc is doing operations on a very write heavy table.

One way to fix this is to have pt-osc fetch the data and perform traditional 'insert into .... values ()',which is not a bulk insert and does not hold the AUTO-INC lock

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.