<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DataStax Support Forums &#187; Topic: Opscenter space usage</title>
		<link>http://www.datastax.com/support-forums/topic/opscenter-space-usage</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Sat, 25 May 2013 18:42:36 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.3</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.datastax.com/support-forums/search.php</link>
		</textInput>
		<atom:link href="http://www.datastax.com/support-forums/rss/topic/opscenter-space-usage" rel="self" type="application/rss+xml" />

		<item>
			<title>mbulman on "Opscenter space usage"</title>
			<link>http://www.datastax.com/support-forums/topic/opscenter-space-usage#post-278</link>
			<pubDate>Thu, 07 Jul 2011 14:33:57 +0000</pubDate>
			<dc:creator>mbulman</dc:creator>
			<guid isPermaLink="false">278@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;This is the expected size for your cluster, but also a known issue. There will be changes in the next version of OpsCenter (July 11) in the way we store data that will reduce this size.  This version will also stop collecting metrics for the system and OpsCenter keyspaces by default, which will cause less data to be stored.&#60;/p&#62;
&#60;p&#62;OpsCenter 1.2.1, slated for late July/early August, will also have more improvements to reduce data size.  It will also expose an option to expire metrics.  This should help significantly for people concerned with disk space who are willing to lose some historical data after a certain amount of time.&#60;/p&#62;
&#60;p&#62;If you notice you have a large number of SSTables for the metrics column family, running a compaction on each node (only if you can sacrifice the performance impact) should reduce the total disk usage.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>apetcu on "Opscenter space usage"</title>
			<link>http://www.datastax.com/support-forums/topic/opscenter-space-usage#post-277</link>
			<pubDate>Thu, 07 Jul 2011 06:56:54 +0000</pubDate>
			<dc:creator>apetcu</dc:creator>
			<guid isPermaLink="false">277@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;What is &#34;normal&#34; Opscenter space usage?&#60;/p&#62;
&#60;p&#62;On my cluster (5 nodes) the directory /var/lib/cassandra/data/OpsCenter/ seems unjustifiably large. On all the nodes in the cluster, there is between 1 and 5 GB of data in this folder, after about a couple of weeks of operation. The culprits seem to be metrics-g-*-Data.db files taking up most of the space.&#60;/p&#62;
&#60;p&#62;Is this normal behaviour? At this rate, space usage is unsustainable, we need to constantly add storage to our cluster nodes.&#60;br /&#62;
Is this a known issue, or do I have a problem with my installation?&#60;/p&#62;
&#60;p&#62;thanks
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
