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

InnoDB: innodb_page_size=x requires innodb_buffer_pool_size > xxx current xx should be logged as an error or a at least a high-priority warning

    XMLWordPrintable

Details

    Description

      10.4 6918157e

      2020-01-31 14:46:58 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4190)
      2020-01-31 14:46:58 0 [Warning] Changed limits: max_open_files: 1024  max_connections: 151 (was 151)  table_cache: 421 (was 2000)
      2020-01-31 14:46:58 0 [Note] Plugin 'partition' is disabled.
      2020-01-31 14:46:58 0 [Note] Plugin 'SEQUENCE' is disabled.
      2020-01-31 14:46:58 0 [Note] InnoDB: innodb_page_size=32768 requires innodb_buffer_pool_size > 24M current 8388608
      2020-01-31 14:46:58 0 [ERROR] Plugin 'InnoDB' init function returned error.
      2020-01-31 14:46:58 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      

      To my understanding, this inconsistency between innodb_page_size and innodb_buffer_pool_size is always fatal for InnoDB, however it is only logged as a Note. It's not easy to figure right away why InnoDB fails to initialize. I think it should be logged as an ERROR as well.

      Attachments

        Activity

          People

            marko Marko Mäkelä
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.