Re: Mysql tuning - server Crash 1 - Heikki Tuuri - com.mysql.lists.mysql

17 messages in com.mysql.lists.mysqlRe: Mysql tuning - server Crash 1

From	Sent On	Attachments
Deluxe Web	26 Feb 2005 02:03
Heikki Tuuri	26 Feb 2005 23:34
Deluxe Web	27 Feb 2005 04:16
Heikki Tuuri	27 Feb 2005 12:57
Donny Simonton	27 Feb 2005 16:00
Van	27 Feb 2005 17:19
Tom Crimmins	27 Feb 2005 20:30
Deluxe Web	27 Feb 2005 22:29
Deluxe Web	27 Feb 2005 23:13
Heikki Tuuri	28 Feb 2005 01:26
Heikki Tuuri	28 Feb 2005 01:34
Deluxe Web	28 Feb 2005 01:43
Heikki Tuuri	28 Feb 2005 01:47
Deluxe Web	28 Feb 2005 01:56
Van	28 Feb 2005 12:53
Tom Crimmins	28 Feb 2005 14:38
Van	28 Feb 2005 14:51

Subject:	Re: Mysql tuning - server Crash 1
From:	Heikki Tuuri (Heik...@innodb.com)
Date:	02/28/2005 01:47:05 AM
List:	com.mysql.lists.mysql

Max,

----- Original Message ----- From: "Deluxe Web" <delu...@gmail.com> Newsgroups: mailing.database.myodbc Sent: Monday, February 28, 2005 11:44 AM Subject: Re: Mysql tuning - server Crash 1

Hi I understand.. I should switch to debian :) but in the meantime what about the innodb buffer pull size Have you seen my variables. I had 8M? Can this be the bottle neck?

yes it may be. Please see:

http://dev.mysql.com/doc/mysql/en/innodb-configuration.html

--Heikki

On Mon, 28 Feb 2005 11:34:31 +0200, Heikki Tuuri <Heik...@innodb.com> wrote:

Max,

maybe the 640 connection piled up because mysqld was hung?

It is not very likely that all those threads would have taken > 3 MB of memory. Usually they take much less.

The best advice is to upgrade to a recent 4.0.xx or 4.1.xx version of MySQL, which may print more info in a hang.

An upgrade to a more recent Fedora Core might also help.

Best regards,

Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php

----- Original Message ----- From: "Deluxe Web" <delu...@gmail.com> Newsgroups: mailing.database.myodbc Sent: Monday, February 28, 2005 9:13 AM Subject: Re: Mysql tuning - server Crash 1

In my .err. file I have

---------------- key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=652 max_connections=1000 threads_connected=640 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2184184 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

---------------

With my 2GB RAM I think I reached the maximum. Shall I consider linux swap memory, which is of 2GB? Please advise. Can you help me undertand if an increase of RAM will fix the problem.

On Sun, 27 Feb 2005 18:00:29 -0600, Donny Simonton <don...@intercosmos.com> wrote:

Heikki, I sent this to a few friends of mine who work on fedora quite a bit.

As a general note, Fedora Cores are not considered stable.

None of them wanted to officially comment, but just asked that you show proof. Especially since most of RH4 is Fedora.

I know I've used FC1, FC2, and FC3. And on fc2 and fc3 the 32 and 64 bit versions. And besides certain ide problems which I would never use on a mysql server anyway, we've never had any problems with fedora at all.

They wanted me to send you some of the benchmarks comparing Fedora, Suse, and some of the other distros using mysql. But the site they sent me which shows fedora beating all of them is currently down.

Oh well.

Donny

-----Original Message----- From: Heikki Tuuri [mailto:Heik...@innodb.com] Sent: Sunday, February 27, 2005 2:58 PM To: mys...@lists.mysql.com Subject: Re: Mysql tuning - server Crash 1

Max,

----- Original Message ----- From: "Deluxe Web" <delu...@gmail.com> Newsgroups: mailing.database.myodbc Sent: Sunday, February 27, 2005 2:17 PM Subject: Re: Mysql tuning - server Crash 1

Hi Heikki,

http://lists.mysql.com/mysql/180583 http://lists.mysql.com/mysql/180581

Running fedora core1 Mysql: 4.0.16-Max-log

If you check http://lists.mysql.com/mysql/180583 (.err) you will see errors.

does that contain ALL relevant info?

Let me know if you have any questions.

You should upgrade to 4.1.10. We might get better error diagnostics then.

As a general note, Fedora Cores are not considered stable.

Thank you. I appreciate your help!!

Best regards,

Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php

Deluxe Web delu...@gmail.com