TAS/EAR MySQL high persistent disk due to large events.idb

Products

• VMware Tanzu Platform - Cloud Foundry

Issue/Introduction

TAS/EAR MySQL persistent disk is showing high disk consumption due to a large events.idb.

 

Environment

TAS/EAR

Cause

This can be due along retention period for audit events, see EAR Tile--->Cloud Controller--->Age of completed tasks pruned from Cloud Controller database.

Resolution

There are two options:

• Reduce retention period
• Increase persistent disk

Reduce retention period

Reduce the retention period for audit events and run Apply Changes.

This will reduce the number of events in ccdb.events table.

Check the number of events before and after modifying the retention period.

NOTE: The events may take some time to be flushed out.

bosh -d <CF deployment> ssh mysql/0
sudo -i
mysql --defaults-file=/var/vcap/jobs/pxc-mysql/config/mylogin.cnf
mysql> use ccdb;
mysql> select count(*) from events;

NOTE: When the entries are removed from events table, the size of events.idb will not reduce. This is expected behaviour and it will keep the space as "free space" inside the file for future writes.

To reduce the size of events.idb file, please contact Tanzu Support.

 

Increase persistent disk

If retention period is as required, then increase the persistent disk size from MySQL VMs.