You can do something like this:
Divide your nodes up into 4 datacenters art1,art2,art3,core
[default@unknown] create keyspace art1 placement_strategy =
'org.apache.cassandra.locator.NetworkTopologyStrategy' and
strategy_options=[{art1:2,core:2}];
[default@unknown] create keyspace art2 placement_strategy =
'org.apache.cassandra.locator.NetworkTopologyStrategy' and
strategy_options=[{art2:2,core:2}];
[default@unknown] create keyspace art3 placement_strategy =
'org.apache.cassandra.locator.NetworkTopologyStrategy' and
strategy_options=[{art3:2,core:2}];
[default@unknown] create keyspace core placement_strategy =
'org.apache.cassandra.locator.NetworkTopologyStrategy' and
strategy_options=[{core:2}];
On Tue, Nov 27, 2012 at 5:02 PM, Artist <jer...@simpleartmarketing.com>wrote:
>
> I have 3 art-servers each has a cassandra cluster.
> Each of the art-servers has config/state information stored in a Keyspaces
> respectively called
> art-server-1-current-state, art-server-2-current-state,
> art-server-3-current-state
>
> in my core server I have a separate Cassandra cluster. I would like to use
> Cassandra to replicate the current-state of each art-server on the core
> cassandra server without sharing that information with any of the
> art-servers.
>
> Is there is a way to replicate the keyspaces to a single Cassandra cluster
> my core without having any peer sharing between the 3 art-servers.
>
> -
> Artist
>
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/selective-replication-of-keyspaces-tp7584007.html
> Sent from the cassandra-u...@incubator.apache.org mailing list archive at
> Nabble.com.
>
