Percona Toolkit moved to https://jira.percona.com/projects/PT

pt-online-schema-change -- Should have an option to NOT drop tables on failure

Bug #998831 reported by Will Gunty
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Medium
Daniel Nichter
Percona Toolkit moved to https://jira.percona.com/projects/PT 2.1.2
2.1
Fix Released
Medium
Daniel Nichter
Percona Toolkit moved to https://jira.percona.com/projects/PT 2.1.2

Bug Description

pt-osc should have an option to not drop the new table on a failure. I just had a failure on an extremely large table (1+B rows) and due to our large buffer pool and an open mysql bug (http://bugs.mysql.com/bug.php?id=64284), the drop of the new table resulted in stalling the server and taking the website down.

Having an option to leave the table and drop it manually would help mitigate this.

Related branches

lp:~percona-toolkit-dev/percona-toolkit/handle-deadlocks-pt-osc
Daniel Nichter: Approve
Diff: 55 lines (+15/-2)
1 file modified
bin/pt-online-schema-change (+15/-2)
Jaime Sicam (jssicam)
tags: added: i23453
Daniel Nichter (daniel-nichter)
tags: added: percona-23453 pt-online-schema-change
removed: i23453
Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

Jay asked for this option, too. Along with the fix for bug 1004551 ("pt-online-schema-change --no-swap-tables causes error"), --no-drop-new-table --no-swap-tables can be used to do all the work and leave the new, altered table and not modify the original table.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-532

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.