simply saw table_open_cache
using the full value of 3000 and once again the same behaviour.
When running "Show open tables" though, we find that the amount of open
tables is only 283 and a count of all tables returned that there is only 381 tables on
the server.
However when
Hi all
I am hoping this mail finds all well.
I have a question about mysql open tables and open_table_cache which I do
not seem to be finding the answer to on the internet.
We are busy investigating an issue on a server where we have erattic
behaviour.
During the times
entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
> Subject: Open Tables
> From: sangpr...@gmail.com
> To: mysql@lists.mysql.com
> Date: Wed, 28 Oct 2009 18:59:44 +0700
>
>
I saw so many open tables in my server, is it dangerous? And if I
execute flush tables what does it impacts to the open tables? Thx.
Willy
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
ens: 657 Flush
tables: 1 Open tables: 512 Queries per second avg: 322.082
The value for Open Tables is 512, which looks suspiciously to me like
it's hit a limit. Is there a way to increase that limit? Or am I
misunderstanding what status is telling me?
I have partially answered
via UNIX socket
Client characterset:latin1
Server characterset:latin1
UNIX socket:/var/lib/mysql/mysql.sock
Uptime: 4 days 14 hours 26 min 56 sec
Threads: 161 Questions: 128065100 Slow queries: 0 Opens: 657 Flush
tables: 1 Open tables: 512 Queries per seco
"John Farkas" <[EMAIL PROTECTED]> wrote:
>
> I am new to mysql so please excuse my ignorance.
>
> I am running mysql on windows 2000 and have noticed that when a table is
> opened to do an insert or update it is not closed after the query is
> finished but is left open.
> Then when I shut down th
What version of MySQL are you running.
Edward Dudlik
Becoming Digital
www.becomingdigital.com
- Original Message -
From: "John Farkas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, 17 June, 2003 13:28
Subject: Open Tables
I am new to mysql so plea
That should have had a question mark.
What version of MySQL are you running?
Edward Dudlik
Becoming Digital
www.becomingdigital.com
- Original Message -
From: "John Farkas" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, 17 June, 2003 13:28
Subject:
John Farkas wrote:
I am new to mysql so please excuse my ignorance.
I am running mysql on windows 2000 and have noticed that when a table is
opened to do an insert or update it is not closed after the query is
finished but is left open.
Then when I shut down the mysql server and do a myisamchk
I am new to mysql so please excuse my ignorance.
I am running mysql on windows 2000 and have noticed that when a table is
opened to do an insert or update it is not closed after the query is
finished but is left open.
Then when I shut down the mysql server and do a myisamchk on the tables
they sh
Hi,
Some time ago i've read that we shouldn't use myisamchk while the mysql
server was running. Now, i don't find where in the manual says something
about it.
I think you should do a "FLUSH TABLES" and ensure that no one touches
the tables (including mysqld) before using myisamchk.
Coudn't you use
Since the http://lists.mysql.com/ archives site is down, I'll have to
ask this question without the benifit of the archives...
I have a (very large) Perl script that has a bad tendency to cause the
following warning from myisamchk:
myisamchk: MyISAM file /var/lib/mysql//table_name.MYI
myisa
I've been experiencing some strange behaviour
in which mysqld will get into an odd state.
When doing certain long-running operations
(see below) on large tables (5-10 million rows;
20-30 columns per row -- mix of varchar and int)
with unique indeces mysqld will occasioanlly get
into a confused s
14 matches
Mail list logo
