High Load on Cassandra: Difference between revisions
Jump to navigation
Jump to search
Created page with 'High loan on Emohawk can be caused by tasks that run during the night (around 3 - 5am) or by an issue with the VPS. High load at 3-5am can usually be ignored, but other issues ne...' |
No edit summary |
||
| Line 6: | Line 6: | ||
* If you cannot log in directly to Emohawk, log in to the dom0 as root and type ''xm console xen01''. You should then be at the Emohawk console and can run commands from there. | * If you cannot log in directly to Emohawk, log in to the dom0 as root and type ''xm console xen01''. You should then be at the Emohawk console and can run commands from there. | ||
* Follow instructions at [[Emohawk (domU) is not responding as expected]] | * Follow instructions at [[Emohawk (domU) is not responding as expected]] | ||
If an issue cannot be put down to Emohawk itself, it's worth seeing what others are doing on the dom0. | |||
* Log in as root on the dom0 and type ''iostat -k -d -N 1 100''. This will view the I/O status each second for the next 100 seconds. | |||
Revision as of 10:16, 8 May 2009
High loan on Emohawk can be caused by tasks that run during the night (around 3 - 5am) or by an issue with the VPS. High load at 3-5am can usually be ignored, but other issues need to be examined as soon as possible.
- If you can log in to Emohawk (the domU), examine the currently running processes by typing ps | aux and top.
- Feel free to restart any high-load processes by usign /etc/init.d/XXX restart as required. These are often apache or pure-ftpd.
- There will often be a load of at least 4 because of the distributed.net process that runs across all four cores.
- If you cannot log in directly to Emohawk, log in to the dom0 as root and type xm console xen01. You should then be at the Emohawk console and can run commands from there.
- Follow instructions at Emohawk (domU) is not responding as expected
If an issue cannot be put down to Emohawk itself, it's worth seeing what others are doing on the dom0.
- Log in as root on the dom0 and type iostat -k -d -N 1 100. This will view the I/O status each second for the next 100 seconds.