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

Log full of [Note] InnoDB: ft_end() after upgrade to MariaDB 10.3.10

Details

    Description

      Is this a developer log only? Am I doing something wrong with my configuration?

      Cut from journalctl -u mariadb

      Oct 24 17:45:33 host1 mysqld[12196]: 2018-10-24 17:45:33 173491 [Note] InnoDB: ft_end()
      Oct 24 17:45:33 host1 mysqld[12196]: 2018-10-24 17:45:33 173491 [Note] InnoDB: ft_end()
      Oct 24 17:45:33 host1 mysqld[12196]: 2018-10-24 17:45:33 173491 [Note] InnoDB: ft_end()
      

      https://dba.stackexchange.com/questions/220961/log-full-of-note-innodb-ft-end-after-upgrade-to-mariadb-10-3-10/221865

      https://github.com/MariaDB/server/blob/10.3/storage/innobase/handler/ha_innodb.cc#L10120

      Attachments

        Activity

          The extra printout has been there ever since MySQL 5.6.4. Later in MySQL 5.6.4 the message started using the common logging interface (instead of emitting directly to the standard error).

          MariaDB Server inherited this bug from upstream, already in version 10.0.9 and 10.1.0. Later, in 10.2.2, the ib_logf() was replaced with ib::info(). I do not know why this was reported against 10.3 only.

          marko Marko Mäkelä added a comment - The extra printout has been there ever since MySQL 5.6.4 . Later in MySQL 5.6.4 the message started using the common logging interface (instead of emitting directly to the standard error). MariaDB Server inherited this bug from upstream, already in version 10.0.9 and 10.1.0. Later, in 10.2.2, the ib_logf() was replaced with ib::info() . I do not know why this was reported against 10.3 only.

          For the record, the commit message of the contributed fix was missing a reference to this MDEV.

          marko Marko Mäkelä added a comment - For the record, the commit message of the contributed fix was missing a reference to this MDEV.
          hrvoj3e Hrvoj3e added a comment - - edited

          @Marko Mäkelä My upgrade path was MariaDB 10.2.18 to MariaDB 10.3.10.
          On 10.2.18 the log was clean.

          hrvoj3e Hrvoj3e added a comment - - edited @Marko Mäkelä My upgrade path was MariaDB 10.2.18 to MariaDB 10.3.10 . On 10.2.18 the log was clean.

          People

            marko Marko Mäkelä
            hrvoj3e Hrvoj3e
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.