[MDEV-12609] Allow suppression of InnoDB log messages about reserving extents Created: 2017-04-27  Updated: 2020-08-25  Resolved: 2017-06-08

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0.30, 10.1.22
Fix Version/s: 10.1.25, 10.0.32

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: innodb

Issue Links:
Relates
relates to MDEV-8386 MARIADB creates very big tmp file > 3... Closed

 Description   

A user is constantly seeing messages like the following:

2017-04-23 23:47:44 139336886889216 [Note] InnoDB: Space id 1131 trying to reserve 3 extents actually reserved 256 reserve 7010 free 201 size 44857344 rounds 51 total_reserved 13056
 
2017-04-23 23:47:44 139336886889216 [Note] InnoDB: Space id 1131 trying to reserve 3 extents actually reserved 256 reserve 7011 free 205 size 44857600 rounds 52 total_reserved 13312

It looks like these messages were added as part of the fix for MDEV-8386.

These messages are causing the user's error log to grow very large.

Would it be possible to make some way to suppress these log messages? Maybe they can be changed to warnings, and then suppressed by decreasing log_warnings? Or maybe it can be controlled by some other variable?

 Comments   
Comment by Marko Mäkelä [ 2017-06-05 ]

I would suggest to remove this output, or make it conditional on global_system_variables.log_warnings > 2, like MDEV-10509 did to the output that MDEV-6812 introduced for ALTER TABLE…ALGORITHM=INPLACE.

Comment by Jan Lindström (Inactive) [ 2017-06-08 ]

commit d03abc71a490f4ee6d173d07c95a2adb9c60457c
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Thu Jun 8 10:34:10 2017 +0300

MDEV-12609: Allow suppression of InnoDB log messages about reserving extents

Removed this output.

Generated at Thu Feb 08 07:59:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.