pt-online-schema-change -- Should have an option to NOT drop tables on failure
Bug #998831 reported by
Will Gunty
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 | ||
2.1 |
Fix Released
|
Medium
|
Daniel Nichter |
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://
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 modifiedbin/pt-online-schema-change (+15/-2)
tags: | added: i23453 |
tags: |
added: percona-23453 pt-online-schema-change removed: i23453 |
To post a comment you must log in.
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.