top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

open files in mysqld 5.1.53

0 votes

I am trying to understand the incredible use of filepointers in our mysql server (5.1.53). under normal condition the server reports 10k-15k open files pointer. I run a 'flush tables' every 2h to avoid problems, the number of users/connections is constant
It is an automatic system but a few human users, a happy mix of myisam and innodb tables running
with no problems on mysqld 5.0 . But now sometimes i am hit with an insane increase hitting the ceiling at 60k. I do not like the idea to increase the limit further because i do not understand why this is happening (I seems to happen at random times).

I am running out of idea what my cause the unexpected increase, any idea what to watch ?

posted Jun 12, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

harmless :-)

[root@localhost:~]$ lsof | grep mysqld | wc -l

nobody but oracle knows why there are so much file handles and this is MySQL 5.5.32

answer Jun 12, 2013 by anonymous
Similar Questions
+1 vote

For a Wordpress website I have installed mysql-server-5.1.69-1.el6_4.x86_64 and run /usr/bin/mysql_secure_installation on a CentOS 6.4 machine with mucho RAM (32 GB) and I wonder, what would be the best place for the mysqld parameters descibed at

mysqld_safe --key_buffer_size=64M --table_open_cache=256  --sort_buffer_size=4M --read_buffer_size=1M &

Should I just edit the file /etc/init.d/mysqld or is there a better place in CentOS for that (under sysconfig?)

0 votes

The MySQL 5.7 changelog mentions:
"Beginning with MySQL 5.7.2, UPDATE_TIME displays a timestamp value for the last UPDATE, INSERT, or DELETE performed on InnoDB tables. Previously, UPDATE_TIME displayed a NULL value for InnoDB tables. For MVCC, the timestamp value reflects the COMMIT time, which is considered the last update time. Timestamps are not persisted when the server is restarted or when the table is evicted from the InnoDB data dictionary cache."

This is great news! However, I would in fact need the UPDATE_TIME to persist across database server resets. Is this feature being considered or discussed? Where might I find it online?

+1 vote

Using Workbench with MySQL 5.6 how do I edit a existing Trigger. Do I need
to DROP the Trigger and create a new one ? If that is the case how can you
run start command in a live environment ?

0 votes

I 've just created some tables that I designed using the MySQL Workbench Model. However, the database type BOOLEAN which was in my models has been converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on Windows 2008 server.

Any ideas why this has been removed ?