[MDEV-17918] InnoDB sometimes prints incorrect buffer pool size in the "Over xx percent of the buffer pool is occupied" message - Jira

XML

Word

Printable

10.3 b6f203984bc519a31ac695cbcb6de7f1f638d321
...
2018-12-05 11:39:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
...
2018-12-05 11:39:31 17 [Warning] InnoDB: Over 67 percent of the buffer pool is occupied by lock heaps or the adaptive hash index! Check that your transactions do not set too many row locks. innodb_buffer_pool_size=127M. Starting the InnoDB Monitor to print diagnostics.
...
2018-12-05 11:44:12 18 [ERROR] [FATAL] InnoDB: Over 95 percent of the buffer pool is occupied by lock heaps or the adaptive hash index! Check that your transactions do not set too many row locks, or review if innodb_buf
fer_pool_size=127M could be bigger.
...

Note 127M in the error messages vs. 128M upon initialization (default value).
It doesn't always happen, in most cases it prints 128M as expected.

I have no information whether it happens with other server versions or other buffer pool sizes.

relates to

MDEV-24813 Locking full table scan fails to use table-level locking

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.