OOM error when backing up using --lock-ddl-per-table

Description

 

Issue

Xtrabackup errors with an out of memory message and a reference to a partitioned table.

Versions 

  • mysql Ver 14.14 Distrib 5.7.21-20

  • xtrabackup version 2.4.12 based on MySQL server 5.7.19 Linux (x86_64) (revision id: 170eb8c)

Log Error output

181018 14:07:21 >> log scanned up to (186038457510)
181018 14:07:22 >> log scanned up to (186038457811)
181018 14:07:23 >> log scanned up to (186038458205)
xtrabackup: Out of memory (Needed 1583040 bytes)
Error: failed to fetch query result SELECT * FROM lol_store.transaction_syncs#P#p20180725 LIMIT 1: MySQL client ran out of memory

 

Observations

We also noticed the xtrabackup process uses a large amount of memory

IF you take the SQL in the xtrabackup log output and run and run `SELECT * FROM lol_store.transaction_syncs#P#p20180725 LIMIT 1:` it will scan all (hundreds of the partitions) 

I did not understand why the syntax in the log output from xtrabackup was not 

`SELECT id FROM lol_store.transaction_syncs partition (p20180725) LIMIT 1;`

 

Contacts

awhitwham@riotgames.com

cbegin@riotgames.com

 

 

 

Environment

None

Attachments

1

Activity

adrian whitwham October 25, 2018 at 6:50 AM

Thanks for the quick response. Look forward , as always, to the next release of a brilliant product. 

Sergei Glushchenko October 25, 2018 at 12:07 AM

Thank you for the bug report. I am aware that --lock-ddl-per-table causing this. It will be fixed in the next 2.4.x release.

Done

Details

Assignee

Reporter

Time tracking

1d 1h logged

Fix versions

Affects versions

Priority

Created October 24, 2018 at 5:51 PM
Updated March 6, 2024 at 7:24 PM
Resolved December 13, 2018 at 11:34 AM