[MDEV-24340] Unique final message of InnoDB during shutdown Created: 2020-12-03  Updated: 2021-02-01  Resolved: 2020-12-04

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.2.37, 10.3.28, 10.4.18, 10.5.9

Type: Bug Priority: Major
Reporter: Matthias Leich Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MDEV-24751 runtime error: member call on null po... Closed

 Description   

Please create some unique message to be written by InnoDB into the server error log
which signals that InnoDB will stop its activity (processes and/or threads) immediate.
Such a message would be a significant advantage for QA when classifying suspicious effects.
 
One example of behaviour in 10.6
[Note] ... /bin/mysqld (initiated by: root[root] @ localhost [127.0.0.1]): Normal shutdown
...
Note] InnoDB: Starting shutdown...
[Note] InnoDB: Dumping buffer pool(s) to ... data/ib_buffer_pool
[Note] InnoDB: Buffer pool(s) dump completed at 201202 19:59:02
[Note] InnoDB: Shutdown completed; log sequence number 3153035; transaction id 4930
[Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
[Note] ... bin/mysqld: Shutdown complete
 
I would prefer to have an order of InnoDB related messages like
  [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 
        or whatever InnoDB likes to tell
  [Note] InnoDB: Shutdown completed;  <and whatever extra info in the same line>
  < no line written by InnoDB because it has really finished its work>
  [Note] ... bin/mysqld: Shutdown complete
for all currently supported and future MariaDB versions



 Comments   
Comment by Marko Mäkelä [ 2020-12-04 ]

The problem appears to be that a function innobase_space_shutdown() will be called after the actual innodb_shutdown(). I believe that we do not need that separate function at all; the steps can be executed in innodb_shutdown() or innobase_init_abort().

Generated at Thu Feb 08 09:29:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.