pt-variable-advisor does not consider innodb-plugin

Reported by Giovanni Bechis on 2012-03-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Medium
Unassigned

Bug Description

If innodb-plugin is enabled in MySQL 5.1.x, pt-variable-advisor give a note abot the variable "innodb_max_dirty_pages_pct" too low.
If innodb-plugin is enabled this variable has a different default than with internal innodb storage.

http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#sysvar_innodb_max_dirty_pages_pct

Maybe other parameters have different defaults too.

---------------------
$ pt-variable-advisor h=host,u=root --ask-pass
Enter password:
# NOTE innodb_max_dirty_pages_pct: The innodb_max_dirty_pages_pct is lower than the default.

On server I am using MySQL 5.1.61

  Giovanni

Baron Schwartz (baron-xaprb) wrote :

Thank you for the bug report. Indeed, the default did change with the plugin, and what we should do is warn if the setting is non-default. We can avoid a lot of complex logic by just testing whether the value is equal to the default in the old or new version, regardless of the actual version running.

Changed in percona-toolkit:
status: New → Confirmed
importance: Undecided → Medium

On 03/08/12 18:39, Baron Schwartz wrote:
> Thank you for the bug report. Indeed, the default did change with the
> plugin, and what we should do is warn if the setting is non-default. We
> can avoid a lot of complex logic by just testing whether the value is
> equal to the default in the old or new version, regardless of the actual
> version running.
>
It could be fine but we should handle different default parameters in
different MySQL versions too.
Maybe something like this could be used:
if ($mysql_ver -eq 5.0) {
 %default_var = ('var1' => 'value1','var2' => 'value2');
} elseif....

 Giovanni

tags: added: pt-variable-advisor
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers