innobackupex invoke OOMkiller when using lock-ddl-per-table
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
New
|
Undecided
|
Unassigned |
Bug Description
Story.
I have a large MariaDB-10.2.8 InnoDB installation (850Gb), with multimaster replication and also act as master for it own databases.
When i try do backup i get:
# innobackupex --user backup --password PASS --stream=tar ./ | nc blackbox-03.mysql 7000
...
InnoDB: Last flushed lsn: 12412902447068 load_index lsn 12414483598158
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.
MariaDB does not support LOCK TABLES FOR BACKUP asn i can't use --lock-ddl
I try use:
innobackupex --lock-
And some time laster it invoke OOMkiller. My VM have 48Gb memory and 22Gb usually is free.
Affected version:
percona-
percona-
So, i can't do backup any way i choose.
Hi,
Could you please paste the output of dmesg, to see the OOM killer message?