Skip to content

Wrong report of InnoDB Storage engine status #450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
schemacs opened this issue Aug 15, 2019 · 1 comment
Closed

Wrong report of InnoDB Storage engine status #450

schemacs opened this issue Aug 15, 2019 · 1 comment
Assignees
@jmrenouard
Labels
bug

Comments

@schemacs
Copy link

if run with --skipsize, the report says:

[!!] InnoDB Storage engine is disabled. InnoDB is the default storage engine

for enginestats is not collected at

MySQLTuner-perl/mysqltuner.pl

Line 5491 in ece5671

&& defined $enginestats{'InnoDB'} )

so this wrong warning is the side effect of --skipsize?
@jmrenouard jmrenouard self-assigned this Sep 25, 2019
@jmrenouard jmrenouard added the bug label Sep 25, 2019
@jmrenouard
Copy link
Collaborator

Now message is
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] Skipped due to --skipsize option

jmrenouard added a commit that referenced this issue Sep 25, 2019
@jmrenouard
Wrong report of InnoDB Storage engine status #450
7332f8d 
Good message is
-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] Skipped due to --skipsize option
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmrenouard jmrenouard

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@schemacs @jmrenouard