SHOW ENGINE INNODB STATUS output filled by deadlock output

Bug #300654 reported by Evgeniy Stepchenko
2
Affects Status Importance Assigned to Milestone
Percona patches
Fix Released
Medium
Unassigned
Percona-XtraDB
Fix Released
Medium
Unassigned

Bug Description

There is a bug
http://bugs.mysql.com/bug.php?id=19825

Which manifests itself by truncating the output of 'SHOW ENGINE INNODB
STATUS' because the deadlock output is to large.

This causes problems because our cacti templates are relying on that
information to graph innodb activity.

Baron actually suggested in the bug report why not move that section to
the end. Is there any chance we could do something about this in the
Percona patched versions.

Revision history for this message
Evgeniy Stepchenko (evgeny-stepchenko) wrote :

Yasufumi, please investigate this issue and propose solution

Changed in percona-patches:
assignee: nobody → yasufumi-kinoshita
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

I think it is not good to move the section to the end of 'SHOW INNODB STATUS'.
If do so, the important data will be scrolled out by the large output of the end section....

Revision history for this message
Vadim Tkachenko (vadim-tk) wrote :

Yasufumi, if it is not at the end of 'SHOW INNODB STATUS', then important data may not appear at all in output, as it will be truncated to 64K

Revision history for this message
Evgeniy Stepchenko (evgeny-stepchenko) wrote :

it was fixed in the initial XtraDB release

Changed in percona-xtradb:
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → yasufumi-kinoshita
status: Confirmed → Fix Released
Revision history for this message
Yasufumi Kinoshita (yasufumi-kinoshita) wrote :

I will fix as the current XtraDB does.

Changed in percona-xtradb:
assignee: yasufumi-kinoshita → nobody
Changed in percona-patches:
status: Confirmed → Fix Committed
Changed in percona-patches:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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