High Load on Cassandra - Revision history

Proaxxs at 22:45, 6 April 2014

2014-04-06T22:45:08Z

← Older revision		Revision as of 22:45, 6 April 2014
Line 1:		Line 1:
	High ~~loan~~ on Cassandra (the main domU on node00004) 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.		High load on Cassandra (the main domU on node00004) 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 Cassandra (the domU), examine the currently running processes by typing ''ps \| aux'' and ''top''.		* If you can log in to Cassandra (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.		* Feel free to restart any high-load processes by using ''/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 [http://www.distributed.net/ distributed.net] process that runs across all four cores.		* There will often be a load of at least 4 because of the [http://www.distributed.net/ distributed.net] process that runs across all four cores.
	* If you cannot log in directly to Cassandra, 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 Cassandra, 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.

Cocodude at 07:00, 4 July 2012

2012-07-04T07:00:53Z

← Older revision		Revision as of 07:00, 4 July 2012
Line 9:		Line 9:
	If an issue cannot be put down to Cassandra itself, it's worth seeing what others are doing on the dom0.		If an issue cannot be put down to Cassandra 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.		* Log in as root on the dom0 and type ''iostat -k -d -N 1 -z 100''. This will view the I/O status each second for the next 100 seconds.

Cocodude at 17:06, 29 November 2010

2010-11-29T17:06:57Z

← Older revision		Revision as of 17:06, 29 November 2010
Line 1:		Line 1:
	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.		High loan on Cassandra (the main domU on node00004) 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''.		* If you can log in to Cassandra (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.		* 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 [http://www.distributed.net/ distributed.net] process that runs across all four cores.		* There will often be a load of at least 4 because of the [http://www.distributed.net/ 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.		* If you cannot log in directly to Cassandra, 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 [[Cassandra (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.		If an issue cannot be put down to Cassandra 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.		* 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.

Cocodude: moved High Load on Emohawk to High Load on Cassandra

2010-11-29T17:06:03Z

moved High Load on Emohawk to High Load on Cassandra

← Older revision	Revision as of 17:06, 29 November 2010
(No difference)

Cocodude at 10:16, 8 May 2009

2009-05-08T10:16:46Z

← Older revision		Revision as of 10:16, 8 May 2009
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.

Cocodude: 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...'

2009-05-05T13:09:54Z

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...'

New page

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 [http://www.distributed.net/ 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]]