Issues with linode

You're looking at this backwards. What you are experiencing is not Linode throttling your disk IO, which chokes mysql.

That email you are getting is just a warning which notifies you of what your node is doing.

If you dig into your logs and configs, you're going to discover that some problem between nginx/your site/mysql is causing your server to eat up all its RAM, causing it to push into swap space, which is thrashing your disk IO and generating the email alert.

Also, the Linode Library has guides for setting up HA.

You're probably swapping a lot.

How are you running php? Can you show your mysql configuration?

It sounds like you're running out of memory.

The high IO rate isn't the root problem, it's a symptom. Your node is running out of memory and hitting your swap space very hard (which obviously involves a lot of disk io). There isn't any "threshold" as far as your node is concerned, that's the just threshold at which you get notified. You can adjust that threshold up and down in the control panel.

The issues you're experiencing have nothing to do with Linode in particular, any Linux server under the same conditions (your configuration, load, and available resources) would be acting the same way.

I'd look at reducing your memory usage. How are you running PHP? If you're using php-fpm, what's your max_children setting set at? My guess is you're spinning up too many php fcgi processes.

You should also look into optimizing MySQL. mysqltuner.pl is a great script to get you started there. Run it, research the settings it suggests you change, and then tweak them appropriately.

Thanks for the reply.

I am using php-fpm

I am putting few lines from configuration files which may be useful for diagnosing problem

MySql config file

[mysqld]

datadir=/var/lib/mysql

socket=/var/lib/mysql/mysql.sock

user=mysql

[mysqld_safe]

log-error=/var/log/mysqld.log

pid-file=/var/run/mysqld/mysqld.pid

php.ini

[Pdo]

;pdoodbc.connectionpooling=strict

;pdoodbc.db2instance_name

[Pdo_mysql]

pdomysql.cachesize = 2000

pdomysql.defaultsocket=

[MySQL]

mysql.allowlocalinfile = On

mysql.allow_persistent = On

mysql.cache_size = 2000

mysql.max_persistent = -1

mysql.max_links = -1

mysql.default_port =

mysql.default_socket =

mysql.default_host =

mysql.default_user =

mysql.default_password =

mysql.connect_timeout = 60

mysql.trace_mode = Off

php-fpm.conf

listen = 127.0.0.1:9000

listen.backlog = -1

listen.allowed_clients = 127.0.0.1

pm = dynamic

pm.max_children = 50

pm.minspareservers = 5

pm.maxspareservers = 20

pm.max_requests = 500

I guess tht pm.max_children may be the root cause.

By the way, Do you know any open source (or free) load test tool so that I can test my website before making it public.

Thanks again for your valuable suggestions.

Are you sure you can manage your server? Read guides.

http://library.linode.com/

> Are you sure you can manage your server? Read guides.

http://library.linode.com/

I am a newbie as web-admin. I guess there is no harm in asking a question for getting help.

drop max children to 4.

@rajeevku02:

I am a newbie as web-admin. I guess there is no harm in asking a question for getting help.
No harm in reading these guides too, be sure. It's very useful.

A mistake often made is when people don't close their mysql connection in their php code after the page has parsed, thus creating additional connections everytime and eventually makes mysql deny additionnal connections/run out of memory.

~~@http://php.net/manual/en/function.mysql-close.php:~~

Using mysql_close() isn't usually necessary, as non-persistent open links are automatically closed at the end of the script's execution.