INNODB STATUS extensions break tools

Bug #1114321 reported by Sergei Golubchik on 2013-02-03
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Won't Fix
Undecided
Unassigned
5.5
Won't Fix
Undecided
Unassigned
5.6
Triaged
Wishlist
Unassigned
5.7
Triaged
Wishlist
Unassigned

Bug Description

Munin (http://munin-monitoring.org/) parses SHOW INNODB STATUS output, and reportedly [1] it expects every section to have a header like

--------------
ROW OPERATIONS
--------------

The OLDEST VIEW part looks different, and it breaks munin monitoring.

[1] https://mariadb.atlassian.net/browse/mdev-4129

Vadim Tkachenko (vadim-tk) wrote :

This should be fixed in Munin,
as whole idea of improvement in XtraDB is to provide more information.
If Munin can't handle it , it is not our bug.

Sergei Golubchik (sergii) wrote :

I mean, you could print "OLDEST VIEW" as

-----------
OLDEST VIEW
-----------

to make it look similar to other sections in the SHOW INNODB STATUS.

It's still munin bug that it complains for "OLDEST VIEW" section, and this bug is filed as http://munin-monitoring.org/ticket/1302 but currently "OLDEST VIEW" doesn't even follow the conventional SHOW INNODB STATUS syntax.

tags: added: xtradb

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2402

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.