Bug #35971 Enterprise Monitor record purge does not free disk space.

• Submitted: 10 Apr 2008 19:26
• Modified: 13 Jan 2009 14:34
• Reporter: Matthew Montgomery
• Status: Closed
• Category: MySQL Enterprise Monitor: Configuration
• Severity: S4 (Feature request)
• Version: 1.3.0
• OS: Any
• Assigned to: Tony Bedford
• CPU Architecture: Any

[10 Apr 2008 19:26] Matthew Montgomery

Description:
Since the `merlin` database for MySQL Enterprise Monitor uses InnoDB there is no way to reduce the size of the data files after an old log/event data purge operation.

I would like to see MEM enable the innodb_file_per_table option by default.  This will allow the user to reclaim space from deleted rows in the tablespace by doing an OPTIMIZE TABLE operation.

Currently the purge data operation executes once a day,  However there is no option to trigger the purge operation manually.

How to repeat:
.

Suggested fix:
.

[6 Nov 2008 8:56] Mark Leith

This is now completed in 2.0. 

It is not set during the upgrade however, only on new installations. 

Suggest documenting how to reclaim the space (using OPTIMIZE TABLE) within the documentation on purge settings as well.

[13 Jan 2009 14:34] Tony Bedford

A note was added to the Purge Settings section of the main documentation as requested.

An entry was added to the 2.0 changelog:

Since the repository database for MySQL Enterprise Monitor uses InnoDB there was no way to reduce the size of the data files after an old log/event data purge operation. Further, the purge data operation executed once per day, and had no option to trigger the purge operation manually.