Bug #23552 Error log: "InnoDB: Warning: purge reached the head of the history list..."
Submitted: 23 Oct 2006 14:12 Modified: 14 Feb 2007 14:42
Reporter: Igor Zhbanov Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:4.1.21 OS:Linux (SUSE LINUX 10.1 (X86-64))
Assigned to: Heikki Tuuri CPU Architecture:Any
Tags: corruption

[23 Oct 2006 14:12] Igor Zhbanov
Description:
Hello!

I see these messages in error log of MySQL about every 5 minutes:
061023  9:31:03  InnoDB: Warning: purge reached the head of the history list,
InnoDB: but its length is still reported as 9459212! Make a detailed bug
InnoDB: report, and post it to bugs.mysql.com

So, I post it as it was suggested. ;-)

Here is my.cnf:
------------------------------------------------------------------------------
[client]
#password       = your_password
port            = 3306
socket          = /tmp/mysql.sock

[mysqld]
port            = 3306
socket          = /tmp/mysql.sock
skip-locking

key_buffer = 384M
max_allowed_packet = 1M
table_cache = 512
sort_buffer_size = 2M
read_buffer_size = 2M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 32M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8

#cache
query_cache_limit=256M
query_cache_type=1

default-character-set=cp1251
low_priority_updates=1

set-variable = long_query_time=15
log-long-format
log-slow-queries = /usr/local/mysql/data/mysqld.slow.log

#innodb
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
set-variable = innodb_buffer_pool_size=768M
set-variable = innodb_additional_mem_pool_size=100M
# Set .._log_file_size to 25 % of buffer pool size

set-variable = innodb_log_file_size=10M
#set-variable = innodb_log_buffer_size=10M

#for transactions
innodb_flush_log_at_trx_commit = 1

set-variable = innodb_lock_wait_timeout=50

#for recovery
#set-variable = innodb_force_recovery=5

[isamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqldump]
quick
max_allowed_packet = 16M
------------------------------------------------------------------------------

If you need Any additional info, just ask. I'm programmer a bit ;-), so I can even debug MySQL or install custom version from source.

Thanks.

How to repeat:
Don't know. Messages appears every 5 minutes.
[23 Oct 2006 15:18] Heikki Tuuri
Hi!

I have seen a few of these reports on the mailing lists lately, but unfortunately, I do not know what may cause this. It might be ibdata corruption, but apparently nothing too serious.

We may add diagnostic code to InnoDB so that we will eventually find out what is the reason for this.

Regards,

Heikki
[10 Jan 2007 17:52] Heikki Tuuri
http://bugs.mysql.com/bug.php?id=25484 looks like a duplicate of this.