I do a lot of work with my Linode that currently hosts a site, but every now and then (usually once every two months or so) - I'll get a warning about my IO rate being too high (Usually just higher than 6000). The last one I got said: "Your Linode ... has exceeded the notification threshold (1000) for disk io rate by averaging 6557.69 for the last 2 hours".

I'm a bit worried about this, but don't really know what to think. Is it healthy? Looking at my server graphs I never see anything special, below are two 'regular' days for my low traffic site (note that the two major spikes are my rsyncing to backup the server). Also note that even though I rsynced twice that day, I didn't get a warning come through about those. The graphs are as follows: IO Rate: http://i.imgur.com/vLo7A.png

Traffic: http://i.imgur.com/OIHT9.png

I've tried looking at iotop but whenever I take a look everything looks healthy.

Any ideas?

Thanks In Advance,

Regards,

Joe

link|improve this question

Could it just be that I rsynced a lot of times in an hour that day or something? I'm not sure, I can't remember what I was doing the last time I got the error. – Joesavage1 Nov 22 '11 at 7:43
Where did you get this warning "Your Linode ... has exceeded the notification threshold..."? – quanta Nov 22 '11 at 8:53
@quanta It was emailed to me via some automatic thing wired up to my Linode. – Joesavage1 Nov 22 '11 at 15:18
feedback

2 Answers

up vote 1 down vote accepted

6557 per hour means less than two disk operations per second. 6557 per two hours means less than one per second. Your only problem seems to be overly sensitive notification threshold.

I would investigate if I've got 50.000 per hour or so (but this still would not constitute a real problem).

link|improve this answer
It doesn't say per two hours though, it says "averaging". So it could be 6557 per second for the last two hours, I don't know - it doesn't say in the emails. Any ideas on further investigation? – Joesavage1 Nov 22 '11 at 15:20
feedback

Disk IO are writes and reads to/from disk. I know nothing about your stack, but a common cause for spikes that don't correspond to traffic are log rotations/compression.

link|improve this answer
Any tips on how to reduce this? – Joesavage1 Nov 22 '11 at 19:01
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.