Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4129

INNODB STATUS different output MySQL vs MariaDB

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Won't Fix
        • Affects Version/s: 5.5.29
        • Fix Version/s: None
        • Component/s: None
        • 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.

            Gliffy Diagrams

              Attachments

                Issue Links

                links to

                Web Link 1302: MariaDB cannot parse InnoDB

                Web Link lp:1114321 INNODB STATUS extensions break tools

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  mahdi Petr Mahdi added a comment -

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

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

                  Show
                  mahdi Petr Mahdi added a comment - It tooks \n in ROW OPERATIONS it's of course -------------- ROW OPERATIONS -------------
                  Hide
                  Permalink
                  serg Sergei Golubchik added a comment -

                  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.

                  Show
                  serg Sergei Golubchik added a comment - 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.
                  Hide
                  Permalink
                  mahdi Petr Mahdi added a comment -

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

                  Show
                  mahdi Petr Mahdi added a comment - Thanks, here's related munin defect - http://munin-monitoring.org/ticket/1302

                    People

                    • Assignee:
                      Unassigned
                      Reporter:
                      mahdi Petr Mahdi
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      3 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: