You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this error while installing the plugin:
Output from SHOW ENGINE INNODB STATUS was truncated.
This happens if the output of SEIS exceeds 64KB.
I checked the size of the field returned and it was only about 8KB.
So I dug into the plugin a bit more, and discovered that the parsing algorithm was skipping sections, and I could not work out why, despite trying to follow every match.
In the end, I rewrote it to split the innodb result into an associative array of sections, and then iterate over those, so that every section would be counted.
Now no need for the dummy section, because if 'END OF INNODB MONITOR OUTPUT' isn't defined, then the status was truncated.
The subs, skip_heading and match_new_section are now obsolete.
Updated plugin attached, please review!
The text was updated successfully, but these errors were encountered:
AndyLeeRobinson
changed the title
Parse
Parser finds only every other section of INNODB STATUS result.
Nov 25, 2015
I noticed this error while installing the plugin:
Output from SHOW ENGINE INNODB STATUS was truncated.
This happens if the output of SEIS exceeds 64KB.
I checked the size of the field returned and it was only about 8KB.
So I dug into the plugin a bit more, and discovered that the parsing algorithm was skipping sections, and I could not work out why, despite trying to follow every match.
In the end, I rewrote it to split the innodb result into an associative array of sections, and then iterate over those, so that every section would be counted.
Now no need for the dummy section, because if 'END OF INNODB MONITOR OUTPUT' isn't defined, then the status was truncated.
The subs, skip_heading and match_new_section are now obsolete.
Updated plugin attached, please review!
The text was updated successfully, but these errors were encountered: