The fix for #1555626 should just show an error message and exit, not crash

Bug #1663981 reported by Miguel Angel Nieto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Status tracked in 2.4
2.4
Triaged
Medium
Unassigned

Bug Description

Crashes should only happen when there is a bug in the code.

The fix for the bug #1555626 is to just crash if a DDL is found. That is actually misleading for our users and customers, since they just find a large crash message with a stacktrace that it is actually not needed at all.

This should be handled in a more clean way. It should just stop the process, and show a clear message. Something like:

Backup aborted, error XXX. An optimized (without redo logging) DDL operation has been performed during the copy process that would lead to a corrupted backup. Please, try your backup again.

That easy to read output will save tons of public messages and tickets.

Changed in percona-xtrabackup:
status: New → Confirmed
description: updated
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/PXB-784

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.