Bug #92648 | MySQL process consuming 100% memory | ||
---|---|---|---|
Submitted: | 3 Oct 2018 4:30 | Modified: | 4 Oct 2018 12:12 |
Reporter: | akshaya srinivasan | Email Updates: | |
Status: | Unsupported | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S5 (Performance) |
Version: | 5.6 | OS: | Linux |
Assigned to: | CPU Architecture: | Any (10GB RAM size) | |
Tags: | memory leak, MySQL, mysqldump |
[3 Oct 2018 4:30]
akshaya srinivasan
[4 Oct 2018 12:12]
MySQL Verification Team
Hi, Thank you for your report. I am afraid it is not possible to backup MyISAM tables without flushing tables with the read lock. This is because MyISAM SE is neither ACID nor does it have isolation levels. There are only two things that you can do. One is to plan to move all your tables to InnoDB. The other possibility is to dump each database separately. Also, for your information, this is not a memory leak, since after the backup is finished, all memory is released to the operating system.