MySQL Forums
Forum List  »  InnoDB

Re: InnoDB: ERROR: the age of the last checkpoint
Posted by: alan langridge
Date: August 23, 2006 09:31AM

Hi,

Thanks for coming back to me.

We are running MySQL version 5.0.18-max-log running on Solaris 10 release 0106 X86 64bit.

Good guess! Our log file size is 100M, as show in our my.cnf below:

[client]
port = 3306
socket = /tmp/mysql.sock
[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-locking
key_buffer = 384M
max_allowed_packet = 16M
table_cache = 512
sort_buffer_size = 8M
read_buffer_size = 8M
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
thread_cache_size = 8
query_cache_size = 256M
query_cache_limit = 4M
set-variable=open_files_limit=1100
thread_concurrency = 8
log-error=/<path>/<host>.err
replicate-do-db=db3
replicate-do-db=db2
replicate-do-db=db1
log-bin=<host>-bin
server-id = 1003
basedir=/<path>/mysql
datadir=/<path>
innodb_data_home_dir = /<path>
innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
innodb_log_group_home_dir = /<path>
innodb_log_arch_dir = /<path>
innodb_buffer_pool_size = 2048M
innodb_additional_mem_pool_size = 32M
innodb_log_file_size = 100M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

Also, it may help, but we have recieved this error / warning a number of times in the last days:

060822 18:58:53 InnoDB: ERROR: the age of the last checkpoint is 188740043,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060822 19:00:06 InnoDB: ERROR: the age of the last checkpoint is 191518582,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060822 19:20:34 InnoDB: ERROR: the age of the last checkpoint is 188740415,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060822 19:30:42 InnoDB: ERROR: the age of the last checkpoint is 188740137,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060822 19:33:13 InnoDB: ERROR: the age of the last checkpoint is 188740258,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060822 19:43:20 InnoDB: ERROR: the age of the last checkpoint is 188740360,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060822 19:44:27 InnoDB: ERROR: the age of the last checkpoint is 188740054,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
060823 9:55:50 InnoDB: ERROR: the age of the last checkpoint is 188740053,
InnoDB: which exceeds the log group capacity 188739994.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.

And in the database, the only blob currently has a max length of 25378 bytes.

Hope this all helps solve the mystery :-)

Thanks again,
Alan

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: InnoDB: ERROR: the age of the last checkpoint
12393
August 23, 2006 09:31AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.