<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://gigatux.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Proaxxs</id>
	<title>GigaTux Wiki - User contributions [en-gb]</title>
	<link rel="self" type="application/atom+xml" href="https://gigatux.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Proaxxs"/>
	<link rel="alternate" type="text/html" href="https://gigatux.com/wiki/index.php?title=Special:Contributions/Proaxxs"/>
	<updated>2026-11-07T15:14:00Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>https://gigatux.com/wiki/index.php?title=High_Load_on_Cassandra&amp;diff=602</id>
		<title>High Load on Cassandra</title>
		<link rel="alternate" type="text/html" href="https://gigatux.com/wiki/index.php?title=High_Load_on_Cassandra&amp;diff=602"/>
		<updated>2014-04-06T22:45:08Z</updated>

		<summary type="html">&lt;p&gt;Proaxxs: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.&lt;br /&gt;
&lt;br /&gt;
* If you can log in to Cassandra (the domU), examine the currently running processes by typing &#039;&#039;ps | aux&#039;&#039; and &#039;&#039;top&#039;&#039;.&lt;br /&gt;
* Feel free to restart any high-load processes by using &#039;&#039;/etc/init.d/XXX restart&#039;&#039; as required. These are often apache or pure-ftpd.&lt;br /&gt;
* 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.&lt;br /&gt;
* If you cannot log in directly to Cassandra, log in to the dom0 as root and type &#039;&#039;xm console xen01&#039;&#039;. You should then be at the Emohawk console and can run commands from there.&lt;br /&gt;
* Follow instructions at [[Cassandra (domU) is not responding as expected]]&lt;br /&gt;
&lt;br /&gt;
If an issue cannot be put down to Cassandra itself, it&#039;s worth seeing what others are doing on the dom0.&lt;br /&gt;
&lt;br /&gt;
* Log in as root on the dom0 and type &#039;&#039;iostat -k -d -N 1 -z 100&#039;&#039;. This will view the I/O status each second for the next 100 seconds.&lt;/div&gt;</summary>
		<author><name>Proaxxs</name></author>
	</entry>
</feed>