We've ran into an unusual case where InnoDB Monitor output is flooding the error logs, and eventually leading to disk space issues.
Apparently these cases where the InnoDB Monitor was turned on was triggered by this kind of error message:
Once this occurs, innodb monitor seems to get switched on permanently here, and there does not seem to be a way to stop it that point.
A restart seems to "fix" it temporarily.
Also, explicitly setting innodb_status_output to OFF seems to prevent it (after a restart).
Unlike with long semaphore waits monitor output is enabled permanently here, not just for 30s like with long semaphore waits?
What exactly should we look for in the generated monitor output to track down the root cause?