Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
-
None
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
|
Attachments
Issue Links
- causes
-
MDEV-24751 runtime error: member call on null pointer of type 'struct fil_space_t' in innodb_shutdown
- Closed