InnoDB: An optimized(without redo logging) DDLoperation has been performed.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.4 |
New
|
Undecided
|
Unassigned |
Bug Description
Please refer error dump of xtrabackup :
170103 00:27:52 >> log scanned up to (555158512370)
170103 00:27:53 >> log scanned up to (555158512411)
170103 00:27:54 >> log scanned up to (555158512452)
170103 00:27:55 >> log scanned up to (555158512493)
170103 00:27:56 >> log scanned up to (555158512534)
InnoDB: Last flushed lsn: 555157588339 load_index lsn 555158512534
[FATAL] InnoDB: An optimized(without redo logging) DDLoperation has been performed. All modified pages may not have been flushed to the disk yet.
PXB will not be able take a consistent backup. Retry the backup operation
2017-01-03 00:27:57 0x7f2519c07700 InnoDB: Assertion failure in thread 139797322561280 in file ut0ut.cc line 916
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
18:57:57 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
/usr/bin/
/usr/bin/
/lib/x86_
/lib/x86_
/lib/x86_
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/lib/x86_
/lib/x86_
summary: |
- Xtrabackup failed :: ERROR: non-zero exit status of xtrabackup during - backup. Something may have failed! + InnoDB: An optimized(without redo logging) DDLoperation has been + performed. |
Just noticed that, there was an INDEX creation in progress while backup was in progress.
Could that be a reason for backup failure?
It seems that the bug was fixed though, as per percona release note:
https:/ /www.percona. com/doc/ percona- xtrabackup/ 2.4/release- notes/2. 4/2.4.3. html
Please let me know if more input is needed to investigate further.