We do get some issues related to the ibdata file size and I got this confusion regarding the same. From what I understand in mysql by design the ibdata file size never goes down and it can auto extend to set value based on the entry innodb_data_file_path=ibdata:100M:autoextend:max:<MAX_SIZE> in /etc/my.conf
What happens when ibdata becomes the set MAX_SIZE and i delete the audit events and optimize the tables "audit_main, audit_admin, audit_detail, audit_detail_params, audit_message, audit_system"
Where does the freed up space go ? Does this mean mysql can still write some data= size of cleaned up logs even though the ibdata size shows maximum on the file system? If so can i just do delete audit events and continue using the gateways without downtime and then shrink ibdata on a scheduled time?