[MDEV-17624] Log full of [Note] InnoDB: ft_end() after upgrade to MariaDB 10.3.10 Created: 2018-11-06  Updated: 2018-11-06  Resolved: 2018-11-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.10
Fix Version/s: 10.3.11, 10.2.19, 10.1.38, 10.0.38

Type: Bug Priority: Trivial
Reporter: Hrvoj3e Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu Server 16 LTS



 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



 Comments   
Comment by Marko Mäkelä [ 2018-11-06 ]

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.

Comment by Marko Mäkelä [ 2018-11-06 ]

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

Comment by Hrvoj3e [ 2018-11-06 ]

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

Generated at Thu Feb 08 08:37:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.