[MDEV-21615] InnoDB: innodb_page_size=x requires innodb_buffer_pool_size > xxx current xx should be logged as an error or a at least a high-priority warning Created: 2020-01-31  Updated: 2020-06-01  Resolved: 2020-06-01

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.5.4, 10.2.33, 10.3.24, 10.4.14

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


 Description   

10.4 6918157e

2020-01-31 14:46:58 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4190)
2020-01-31 14:46:58 0 [Warning] Changed limits: max_open_files: 1024  max_connections: 151 (was 151)  table_cache: 421 (was 2000)
2020-01-31 14:46:58 0 [Note] Plugin 'partition' is disabled.
2020-01-31 14:46:58 0 [Note] Plugin 'SEQUENCE' is disabled.
2020-01-31 14:46:58 0 [Note] InnoDB: innodb_page_size=32768 requires innodb_buffer_pool_size > 24M current 8388608
2020-01-31 14:46:58 0 [ERROR] Plugin 'InnoDB' init function returned error.
2020-01-31 14:46:58 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

To my understanding, this inconsistency between innodb_page_size and innodb_buffer_pool_size is always fatal for InnoDB, however it is only logged as a Note. It's not easy to figure right away why InnoDB fails to initialize. I think it should be logged as an ERROR as well.


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