The dumping threads will hold metadata locks progressively while are dumping data.

Bug #1272443 reported by Max Bubenick on 2014-01-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Data Dumper
Max Bubenick

Bug Description

The workaround for that is using SAVEPOINTs within the dumping transactions, but with multiple threads and multiples chunks being dumped in parallel for the same table is not easy to coordinate, we can end up with an inconsistent backup when a TRUNCATE or DROP is executed.

Max Bubenick (max-bubenick) wrote :

this is related to bug #1272310

Changed in mydumper:
milestone: none → 0.6.1
importance: Undecided → Medium
assignee: nobody → Max Bubenick (max-bubenick)
status: New → Triaged
importance: Medium → Wishlist
Changed in mydumper:
status: Triaged → In Progress
Changed in mydumper:
status: In Progress → Fix Committed
Changed in mydumper:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers