Hi! At 11:27 AM 10/30/01 -0000, you wrote: >Sorry for the slow reply here, all has been exceptionally busy... > >We have some tables as InnoDB and some as MyISAM... We upgraded to 4.0 and >the problem went away (we also wanted the ability to change the length of >the stopwords for the fulltext indices. We've found 4 to be exceptionally >stable now that we have the different buffers set optimally, what I think >happened is that we were maxing out the memory for the service even though >we were using the default settings as per the manual althoug our box has >more memory. The site gets hit pretty hard sometimes and I think we were >just pushing too hard. Once we dropped the innodb_buffer_pool_size from 80M >to 40M the speed and stability we'd had before returned and the number of >inserts requiring locks or transactions is far outweighed by those which >don't
Good that 4.0.0 works so well :). But it is still peculiar if mysqld shuts down without printing anything to the MySQL error log. The name of the error log is usually something like 'hostname'.err. Have you looked into it if it contains something special? There was a bug in versions <= 3.23.43 which could cause random crashes. That bug is fixed in 3.23.44 and 4.0.1. I have not tested what happens in Windows 2000 if the OS runs out of memory. In NT a pop-up appears saying that 'the system is running low in virtual memory'. >cheers Heikki > >best wishes >Chris Regards, Heikki http://www.innodb.com >-----Original Message----- >From: Heikki Tuuri [mailto:[EMAIL PROTECTED]] >Sent: Friday, October 26, 2001 8:24 AM >To: [EMAIL PROTECTED]; [EMAIL PROTECTED] >Subject: Re: persistent shutdown of MySQL 3.23.42 Max on Win2K > > >Chris, > >What does InnoDB print to the error log when it >restarts? > >Run mysql-max-nt.exe from the MS-DOS prompt, not >as a service. When it crashes, please send me the >output if any. > >If you have the MS Developer Studio, you should try >running mysqld.exe inside it. When it crashes, please >send me screen captures about the places where it >happened (parameter values, variables, functions >in the stack etc.). > >I found and fixed a bug in 3.23.43 which can cause >random crashes. 3.23.44 should be out next week, and >you could try with it. > >Have you converted your tables to the InnoDB format >or are they MyISAM? > >Do you use BLOBs? > >Regards, > >Heikki > >>Hi Folks >> >>Bit of a puzzle this... we upgraded our MySQL to MySQL-Max on Win2k on a >box >>and the reliability has plummeted, whereas before we were only having to >>restart for maintenance about once a month, we now find it restarts itself >>two or three times a day... any ideas?? The box has 0.5Gb of memory and the >>site is well hit, but hardly goes above 10% of CPU usage... we're using IIS >>and ADO with a couple of Java classes for database access... The error log >>gives us no real insights at all... I've included the my.cnf in case >there's >>something glaring... >>thanks for the help, we're thinking of going back to the non Max version, >>it's be a shame to lose transactions though :-( >>Chris >> >>[mysqld] >>basedir=d:/mysql >>datadir=d:/mysql/data >>innodb_data_file_path = ibdata1:500M;ibdata2:500M >>innodb_data_home_dir = d:\mysql\ibdata >>set-variable = innodb_mirrored_log_groups=1 >>innodb_log_group_home_dir = d:\mysql\iblogs >>set-variable = innodb_log_files_in_group=3 >>set-variable = innodb_log_file_size=30M >>set-variable = innodb_log_buffer_size=8M >>innodb_flush_log_at_trx_commit=1 >>innodb_log_arch_dir = d:\mysql\iblogs >>innodb_log_archive=0 >>set-variable = innodb_buffer_pool_size=80M >>set-variable = innodb_additional_mem_pool_size=10M >>set-variable = innodb_file_io_threads=4 >>set-variable = innodb_lock_wait_timeout=50 >> >>Dr Christopher Thorpe >>Information Architect >>GenomeBiology - biology for the post-genomic era >>w http://www.genomebiology.comt +44 (0) 20 7631 9184 (direct) > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
