[MDEV-4129] INNODB STATUS different output MySQL vs MariaDB Created: 2013-02-03  Updated: 2013-02-03  Resolved: 2013-02-03

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.29
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Petr Mahdi Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

Gentoo, Debian squeeze


 Description   

SHOW ENGINE INNODB STATUS gives extra "separator" ----- in ROW OPERATIONS

This breaks e.g. http://munin-monitoring.org/ which relies on that every section caption is always marked as

-------
SECTION
-------

MariaDB-

--------------
 
ROW OPERATIONS
 
-------------- 
0 queries inside InnoDB, 
0 queries in queue 1 read views open inside InnoDB 
---OLDEST VIEW--- 
Normal read view 
Read view low limit trx n:o 31B2 
Read view up limit trx id 31B2 
Read view low limit trx id 31B2 
Read view individually stored trx ids: 
----------------- 
Main thread process no. 29097, id 2901797696, state: waiting for server activity 
Number of rows inserted 5, updated 27, deleted 4, read 140 
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s

MySQL -

--------------
 
ROW OPERATIONS
 
--------------
 
0 queries inside InnoDB, 
0 queries in queue 1 read views open inside InnoDB 
Main thread process no. 19248, id 2939001664, state: waiting for server activity 
Number of rows inserted 0, updated 0, deleted 0, read 0 
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.00 reads/s

Is it possible to user-definable remove "----------------- " in below?

----------------- 
Main thread process no. 29097, id 2901797696, state: waiting for server

But you should use different separator I guess anyway.

 Comments   
Comment by Petr Mahdi [ 2013-02-03 ]

It tooks \n in ROW OPERATIONS it's of course

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

Comment by Sergei Golubchik [ 2013-02-03 ]

Two comments:
1. We take XtraDB from percona-server, so this bugs should be filed there. I've just did it, feel free to add any information I've missed:
https://bugs.launchpad.net/percona-server/+bug/1114321

This feature was documented here: http://www.percona.com/doc/percona-server/5.5/diagnostics/innodb_show_status.html#oldest-view

2. Even if XtraDB will reformat the output to look like
-----------
OLDEST VIEW
-----------

munin still won't work, it'll abort with the "Unknown section: OLDEST VIEW" error.
I'd suggest to fix it in munin (or file a bug report), to either skip unknown sections or add support for "OLDEST VIEW" section.

Comment by Petr Mahdi [ 2013-02-03 ]

Thanks, here's related munin defect - http://munin-monitoring.org/ticket/1302

Generated at Thu Feb 08 06:53:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.