hmmm, yes... I understand this point quit well... what I was hoping to
learn from the community is:
why does mysql keep the file handles open?
can I do anything (configuration/crafting of SQL statements) that will
prevent mysql from amassing such a large number of open file handles?
what is a reasonable/normal number of file handles for mysql to have open?
For example, I have both linux and mysql configured to allow 64K max files,
will this be sufficient?
Please bear in mind that I realize that you don't know how I've coded my
application, you don't know about my server load, and you don't know about
the hundreds of other variables that could affect this situation... I was
just hoping to get some general information from this group of experienced
mysql "gurus" that might help me avoid stepping in a huge pile of... well,
you know what I mean...
From: Dan Nelson [mailto:dnelson@stripped]
Sent: Friday, June 28, 2002 4:44 PM
To: Sam Taylor
Subject: Re: Increasing number of open_files -- no takers on this one?
In the last episode (Jun 28), Sam Taylor said:
> Greetings All --
> I sent this message to the list a couple of days ago... didn't
> receive any comments/feedback/suggestions...
> if no one knows the answer, can anyone throw me a lifeline and give
> me a suggestion as to how I can go about diagnosing the situation, or
> at least share some of your own experiences (is what I'm seeing
> normal for MySQL??)
open_files is simply the number of filehandles mysql has open. It'll
grow until it hits open_files_limit.
For more info, see http://www.mysql.com/doc/T/a/Table_cache.html