Innodb_buffer_pool_pages_misc value is incorrect

Bug #1311641 reported by Kenny Gryp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Won't Fix
Medium
Unassigned
5.5
Triaged
Medium
Unassigned
5.6
Triaged
Medium
Unassigned
5.7
Triaged
Medium
Unassigned

Bug Description

from SHOW GLOBAL VARIABLES:
| Innodb_buffer_pool_pages_misc | 18446744073709144596 |

The value is quite close to the max bigint value of 18446744073709551615

Percona Server Version: 5.6.15-63.0-log Percona Server (GPL), Release 63.0

Notes that compressed tables are being used.

Innodb Related Configuration:

innodb_buffer_pool_size = 10000M
innodb_additional_mem_pool_size = 16M
innodb_log_file_size = 1G
innodb_buffer_pool_dump_at_shutdown = 1
innodb_buffer_pool_load_at_startup = 1
innodb_log_buffer_size = 8M
innodb_log_files_in_group = 2
innodb_flush_log_at_trx_commit = 2
innodb_flush_method = O_DIRECT
innodb_lock_wait_timeout = 50
innodb_additional_mem_pool_size = 64M
innodb_file_format = barracuda
innodb_file_per_table = 1
innodb_buffer_pool_instances = 4
innodb_write_io_threads = 32
innodb_read_io_threads = 32

Kenny Gryp (gryp)
tags: added: issue-40107
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

Copied 5.1/5.5 status from the upstream bug report.

tags: added: innodb upstream
tags: added: i40107
removed: issue-40107
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-1495

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.