Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.1
-
Fix Version/s: 10.1.7
-
Component/s: Storage Engine - InnoDB, Storage Engine - XtraDB
-
Labels:None
Description
Upon server startup, InnoDB says
2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: The InnoDB memory heap is disabled 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Memory barrier is not used 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Using Linux native AIO 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Not using CPU crc32 instructions 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Completed initialization of buffer pool 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Highest supported file format is Barracuda. 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: 128 rollback segment(s) are active. 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Waiting for purge to start 2015-09-04 2:13:20 139758612277088 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.24-72.2 started; log sequence number 3209317 2015-09-04 2:13:20 139757929621248 [Note] InnoDB: not started
Note the last line.
Even though it's just bad logging (or even bad wording), it's an exceptionally horrible thing to say in the error log, users will freak out. Please fix it.
I don't see it in 10.0 or in MySQL 5.6/5.7, only in 10.1.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
commit 5448e0a6dcf1918f818d162f08dee00e8d6c163e
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Mon Sep 7 08:34:04 2015 +0300
MDEV-8745: Bad InnoDB logging: "[Note] InnoDB: not started"