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

InnoDB status monitor gets enabled after server startup

Details

    Description

      Setting innodb_status_output = 0 in config file has no effect, innodb status is still enabled after server restart (and can be disabled only by executing 'set global innodb_status_output=OFF;').

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14776 InnoDB Monitor output generated by specific error is flooding error logs

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 8 older comments
            azurit azurit added a comment - 

            innodb_buffer_pool_size = 512M

            azurit azurit added a comment - innodb_buffer_pool_size = 512M
            elenst Elena Stepanova added a comment - - edited

            Yes, that's it.
            I assume you didn't change your InnoDB settings recently? Maybe unintentionally?
            Does it start happening right after server startup?
            I'll assign it to an InnoDB expert, hopefully he'll figure out what could have caused the difference. He'll probably request more information from you. Meanwhile, I think the output of show variables won't hurt, and the actual output of the status monitor.

            elenst Elena Stepanova added a comment - - edited Yes, that's it. I assume you didn't change your InnoDB settings recently? Maybe unintentionally? Does it start happening right after server startup? I'll assign it to an InnoDB expert, hopefully he'll figure out what could have caused the difference. He'll probably request more information from you. Meanwhile, I think the output of show variables won't hurt, and the actual output of the status monitor.
            azurit azurit added a comment -

            I have 6 different servers where is this problem occuring but i must say that it's NOT happening on all 10.1.22 servers. I didn't notice it before and i probably would as syslog log files are really full of it (100 MB and more).

            I tested it on one server and innodb_status_output is not enabled immediately after server starts.

            The message above is occuring multiple times per day on every affected server but i wasn't able to find anything which could trigger it - sometimes i can see bigger server load at time when it's logged (the most visible is it on server graphs which i attached, message was logged 5 times at 4:09, by the way, server backup was running at that time).

            azurit azurit added a comment - I have 6 different servers where is this problem occuring but i must say that it's NOT happening on all 10.1.22 servers. I didn't notice it before and i probably would as syslog log files are really full of it (100 MB and more). I tested it on one server and innodb_status_output is not enabled immediately after server starts. The message above is occuring multiple times per day on every affected server but i wasn't able to find anything which could trigger it - sometimes i can see bigger server load at time when it's logged (the most visible is it on server graphs which i attached, message was logged 5 times at 4:09, by the way, server backup was running at that time).
            azurit azurit added a comment -

            I didn't change any settings and i was upgrading from 10.1.20 (we skipped 10.1.21 because of MDEV-11842 ).

            azurit azurit added a comment - I didn't change any settings and i was upgrading from 10.1.20 (we skipped 10.1.21 because of MDEV-11842 ).
            azurit azurit added a comment -

            Anything new? We are really considering moving away from MariaDB back to MySQL because of lots of severe bugs. I'm also trying to resolve MDEV-10011 bud i don't see a thing in logs because of this shit! I'm forced to work with 100 MB logs/day!!

            azurit azurit added a comment - Anything new? We are really considering moving away from MariaDB back to MySQL because of lots of severe bugs. I'm also trying to resolve MDEV-10011 bud i don't see a thing in logs because of this shit! I'm forced to work with 100 MB logs/day!!

            People

              jplindst Jan Lindström (Inactive)
              azurit azurit
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.