Make pt-archiver crash-protected

Bug #1451548 reported by Sveta Smirnova
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Confirmed
Undecided
Unassigned

Bug Description

Currently, if pt-archiver started with option --dest and was killed while doing it job it is possible that chunk of data was copied to destination table, but not deleted from the source table. This can lead to "Duplicate key" error if pt-archiver is restarted.

Please make this operation more crash-safe. For example,

- If --source and --dest are on the same server make INSERTs and DELETE part of single transaction:

BEGIN;
INSERT into dest table ...
DELETE from source table ...
COMMIT;

- If --source and --dest are on different servers make transactions more synchronous:

delete from the source
insert into the destination
commit destination
commit source

- In all cases handle Ctrl-C signal gracefully

Changed in percona-toolkit:
status: New → Confirmed
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-1280

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.