I've been having the same trouble in a Xen virtual machine. After about
an hour and a half, mysql will be consuming 100% of cpu. There is
nothing wrong with the tables. I'm assuming its a dynamic vs. fix
amount of memory available to mysql. I'm guaranteed x amount of ram,
but that might get reduced due to server load. I'm assuming mysql
doesn't like having ram taken away from it and get into a tizzy about it.
I've been forced to restart mysql hourly in order to get smooth operation.
--curtis
Alexey Vlasov wrote:
Hi.
One client from my shared hosting periodically informs me about an
error:
DBI connect('database,...)
failed: Can't create a new thread (errno 12); if you are not out of
available memory, you can consult the manual for a possible OS-dependent
bug at ...
There's nothing suspicious in the MySQL error-log.
# free -m
total used free shared buffers cached
mem: 16039 15794 245 0 2109 6935
-/+buffs/cache: 6748 9290
Swap: 28615 5021 23594
my.cnf:
flush_time = 1800
set-variable = long_query_time=10
set-variable = back_log=1024
set-variable = max_connect_errors=10000000
set-variable = max_connections=640000
set-variable = connect_timeout=20
set-variable = wait_timeout=600
set-variable = interactive_timeout=600
set-variable = table_cache=1000
set-variable = thread_cache_size=16
set-variable = max_tmp_tables=8192
set-variable = max_heap_table_size=64M
set-variable = tmp_table_size=256M
set-variable = max_join_size=50000000
set-variable = key_buffer_size=512M
set-variable = read_buffer_size=128K
set-variable = read_rnd_buffer_size=64K
set-variable = sort_buffer=128M
set-variable = join_buffer_size=64M
set-variable = net_buffer_length=64K
set-variable = query_cache_type=1
set-variable = query_cache_size=256M
set-variable = max_allowed_packet=16M
set-variable = ft_min_word_len=3
# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) 2097152
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 143360
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 143360
virtual memory (kbytes, -v) 4194304
file locks (-x) unlimited
# ps
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
4728 mysql 20 0 2045m 1.0g 5620 S 0 6.3 2602:15 mysqld
# pstree | grep mysql
|-mysqld---29*[{mysqld}]
# mysql --version
mysql Ver 14.12 Distrib 5.0.54, for pc-linux-gnu (x86_64) using
readline 5.2
# uname -a
Linux 2.6.24 #4 SMP Fri Feb 29 20:10:01 MSK 2008
x86_64 Intel(R) Xeon(R) CPU E5345 @ 2.33GHz GenuineIntel GNU/Linux
I would like to know against what limit rests MySQL and whose mistake it
really is, of Perl mysql-client, mysqld or someone else?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
