Bug #100547 | ibdata1 and table space are growing rapidly | ||
---|---|---|---|
Submitted: | 17 Aug 2020 14:15 | Modified: | 18 Aug 2020 13:52 |
Reporter: | Recep Direk | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.6.40 | OS: | Other (Gentoo) |
Assigned to: | CPU Architecture: | x86 | |
Tags: | IBData1, innodb_file_per_table |
[17 Aug 2020 14:15]
Recep Direk
[17 Aug 2020 14:18]
Recep Direk
innodb engine status
Attachment: show engine innodb status.txt (text/plain), 28.66 KiB.
[18 Aug 2020 12:16]
MySQL Verification Team
Hi Mr. Direk, Thank you for your bug report. However, this is not a bug. In the version that you are using, only table data go into the separate tablespaces. Everything else, including redo logs, undo logs, double-write buffers and all other auxiliary, but essential, data go into the system tablespace. Also, all internal InnoDB data dictionaries are in that tablespace as well. This is all described in our 5.6 Reference Manual. Not a bug.
[18 Aug 2020 13:43]
Recep Direk
Hi there, ok I understand this was not a bug. But how can I resolve this issue? Ibdata1 size is growing day by day. Thanks in advance.
[18 Aug 2020 13:47]
MySQL Verification Team
Hi, Please, do note that this is a forum for bug with fully repeatable test cases. And this is not a bug, but expected behaviour. This is not a forum for free support. The only effective way to resolve this is to backup everything, drop all tables , schemas etc, erase everything and start with a new datadir , after which you can restore from backup.
[18 Aug 2020 13:52]
Recep Direk
I see, ok thanks for quick response.