<?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: Star Topology</title>
		<link>http://www.datastax.com/support-forums/topic/star-topology</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Wed, 19 Jun 2013 16:39:21 +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/star-topology" rel="self" type="application/rss+xml" />

		<item>
			<title>dnulu on "Star Topology"</title>
			<link>http://www.datastax.com/support-forums/topic/star-topology#post-8941</link>
			<pubDate>Wed, 06 Feb 2013 16:38:08 +0000</pubDate>
			<dc:creator>dnulu</dc:creator>
			<guid isPermaLink="false">8941@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;After reading the documentation (&#60;a href=&#34;http://www.datastax.com/docs/1.2/index)&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/1.2/index)&#60;/a&#62;, I believe the answer to my question is: yes, this can be achieved with Cassandra 1.2.1 using only configuration settings. Keyspace configuration in particular.&#60;/p&#62;
&#60;p&#62;Replication is specified using a keyspace. There can be multiple keyspaces with different replication strategies. The data-centers to replicate to are specified when the keyspace is created (see the example at &#60;a href=&#34;http://www.datastax.com/docs/1.2/cql_cli/cql/CREATE_KEYSPACE#example-of-setting-the-networktoplogystrategy-class)&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/1.2/cql_cli/cql/CREATE_KEYSPACE#example-of-setting-the-networktoplogystrategy-class)&#60;/a&#62;.&#60;/p&#62;
&#60;p&#62;So with the appropriate keyspace definitions, the star topology described in my question can be achieved.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>dnulu on "Star Topology"</title>
			<link>http://www.datastax.com/support-forums/topic/star-topology#post-8872</link>
			<pubDate>Sat, 02 Feb 2013 08:09:07 +0000</pubDate>
			<dc:creator>dnulu</dc:creator>
			<guid isPermaLink="false">8872@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;I am new to Cassandra and I am trying to determine if I can use the latest version of Cassandra (release 1.2.1) to achieve the following:&#60;/p&#62;
&#60;p&#62;(1) I have many remote sites where &#34;raw&#34; data is gathered and persisted.&#60;br /&#62;
(2) At each remote site, the gathered raw data needs to be aggregated/smoothed.&#60;br /&#62;
(3) This aggregated/smoothed data (not the raw data) must be sent to a central site.&#60;br /&#62;
(4) The aggregated/smoothed data is also persisted at the central site.&#60;br /&#62;
(5) Further aggregation is performed at the central site and the results are persisted at the central site.&#60;/p&#62;
&#60;p&#62;So in essence, the sites form a star-topology.&#60;/p&#62;
&#60;p&#62;(6) The raw data at each remote site should never leave that remote site.&#60;br /&#62;
(7) The aggregated data at each remote site should get persisted only at that remote site and the central site. It should not get replicated to other remote sites.&#60;br /&#62;
(8) When a client reads data at the central site in order to perform further aggregation, the reads should be local to the central site and should not go out to any of the remote sites.&#60;br /&#62;
(9) When a client writes aggregated data to the central site, the writes should stay local to the central site and should not go out to any of the remote sites.&#60;/p&#62;
&#60;p&#62;(10) A WAN connects the remote sites to the central site.&#60;br /&#62;
  (a) If a WAN link between a remote site and the central site goes down, the persisting of raw data and aggregated data should continue at the remote site.&#60;br /&#62;
  (b) Once the WAN link is restored, the aggregated data should get replicated from the remote site to the central site.&#60;/p&#62;
&#60;p&#62;Can Cassandra 1.2.1 achieve the above using only configuration settings? If so, what are the main settings (I am not looking for a configuration file, but just what settings I should focus on).&#60;/p&#62;
&#60;p&#62;If this is not possible with just configuration, is it possible to write some custom code that &#34;plugs into&#34; Cassandra? I am guessing I would need to create a custom partitioner, a custom replication strategy, and a custom snitch.&#60;/p&#62;
&#60;p&#62;Thanks.&#60;/p&#62;
&#60;p&#62;-deepak
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
