pt-stalk should not call mysqladmin debug by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Toolkit moved to https://jira.percona.com/projects/PT |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
mysqladmin debug output is NOT properly documented and is of limited use as a result (see https:/
[openxs@centos git]$ grep -rn MYSQLADMIN `which pt-stalk`
780:CMD_
830: $CMD_MYSQLADMIN $EXT_ARGV debug
894: $CMD_MYSQLADMIN $EXT_ARGV ext -i$OPT_
1011: local open_tables=
2132:=item CMD_MYSQLADMIN
[openxs@centos git]$
...
824 local tail_error_
825 if [ "$mysql_error_log" ]; then
826 log "The MySQL error log seems to be $mysql_error_log"
827 tail -f "$mysql_error_log" >"$d/$p-log_error" &
828 tail_error_
829
830 $CMD_MYSQLADMIN $EXT_ARGV debug
831 else
832 log "Could not find the MySQL error log"
833 fi
834
835 if [ "${mysql_version}" '>' "5.1" ]; then
836 local mutex="SHOW ENGINE INNODB MUTEX"
837 else
838 local mutex="SHOW MUTEX STATUS"
839 fi
840 innodb_status 1
841 tokudb_status 1
...
The outputs of this command pollute error log and force users to ask why is it there when they had NOt explicitly asked for it, wonder is it an indication of a problem etc (imagine pt-stalk working as a daemon and collect9ing statistics periodically).
So, I suggest to disable this call by default and let user enable it if needed with a separate option.
Confirmed as feature request. Personally I never found the debug output useful on any pt-stalk.