Proactive handling of InnoDB tablespace full condition

InnoDB write failures can be encountered due to the underlying file system’s file size limits.

InnoDB logs warnings and error codes (MY-012640 Error number 27 means ‘File too large’), sets an internal tablespace full flag, and may roll back some transactions. However, further modification attempts (inserts/updates) to affected tables will keep failing until administrative action is taken.

For instance, while attempting to write data to the .ibd tablespace file that exceeds file system constraints, the operation fails.

The current InnoDB engine responds by logging the error, but new transactions continue to be accepted and retried, resulting in user disruption, potential data integrity concerns, and soft block corruption in file.

Add proactive monitoring for InnoDB tablespaces by emitting warnings when they approach configured size limits. This feature is specific to InnoDB storage engine and does not affect other storage engines like MyISAM.