Yes that makes sense, thanks Heikki. I monitored the ib_logfiles some more and see the cycling between pairs logfile0+logfile1 and logfile0+logfile2.
Heikki Tuuri wrote:
John,
----- Original Message ----- From: "John Thorpe" <[EMAIL PROTECTED]>
I am running 4.0.4 using innodb tables on a linux box.
My innodb config is
>>set-variable = innodb_mirrored_log_groups=1 >>set-variable = innodb_log_files_in_group=3 >>set-variable = innodb_log_file_size=500M >>set-variable = innodb_log_buffer_size=30M >>innodb_flush_log_at_trx_commit=1 >>innodb_log_archive=0
My question has to do with innodb's usage of the redo log files. Currently they are: 524288000 Mar 11 11:19 ib_logfile0 524288000 Mar 3 08:59 ib_logfile1 524288000 Mar 11 11:19 ib_logfile2 I always see them timestamped like this, with two having identical times, or the same within a minute or two. The particular pair of the three having the same timestamp varies.
the checkpoint stamp fields are in the first ib_logfile. Does that explain the observed phenomenon?
I was under the impression that mysql would cycle through these logfiles - e.g. write to logfile0 until it is full, then switch to logfile1 until full, then logfile2.., then logfile0, etc.
Thanks, John
Best regards,
Heikki Tuuri
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
