Re: Cassandra 1.0.6 multi data center question

[Jeremiah Jordan]

No, not an issue.  The nodes in DC2 know that they aren't supposed to 
have data, so they go ask the nodes in DC1 for the data to return to you.


-Jeremiah

On 02/09/2012 05:28 AM, Roshan Pradeep wrote:

Thanks Peter for the replies.

Previously it was a typing mistake and it should be "getting". I 
checked the DC2 (with having replica 0) and noticed that there is no 
SSTables created.


I use java hector sample program to insert data to the keyspace. After 
I insert a data item, I

1) Login to one of node in DC having replica count 0 using cassanda-cli.
2) Use the keyspace and list the column family.
3) I can see the data item inserted from DC having replica count >1.

Is this a issue? Please clarify. Thanks again.


On Thu, Feb 9, 2012 at 6:00 PM, Peter Schuller 
mailto:peter.schul...@infidyne.com>> wrote:


Again the *schema* gets propagated and the keyspace will exist
everywhere. You should just have exactly zero amount of data for the
keyspace in the DC w/o replicas.


--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)

Re: Cassandra 1.0.6 multi data center question

[Roshan Pradeep]

Thanks Peter for the replies.

Previously it was a typing mistake and it should be "getting". I checked
the DC2 (with having replica 0) and noticed that there is no SSTables
created.

I use java hector sample program to insert data to the keyspace. After I
insert a data item, I
1) Login to one of node in DC having replica count 0 using cassanda-cli.
2) Use the keyspace and list the column family.
3) I can see the data item inserted from DC having replica count >1.

Is this a issue? Please clarify. Thanks again.


On Thu, Feb 9, 2012 at 6:00 PM, Peter Schuller
wrote:

> Again the *schema* gets propagated and the keyspace will exist
> everywhere. You should just have exactly zero amount of data for the
> keyspace in the DC w/o replicas.
>
>
> --
> / Peter Schuller (@scode, http://worldmodscode.wordpress.com)
>

Re: Cassandra 1.0.6 multi data center question

[Peter Schuller]

Again the *schema* gets propagated and the keyspace will exist
everywhere. You should just have exactly zero amount of data for the
keyspace in the DC w/o replicas.


-- 
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)

Re: Cassandra 1.0.6 multi data center question

[Peter Schuller]

> Thanks for the reply. But I can see the data setting inserted in DC1 in DC2.
> So that means data also getting replicated to DC2.

"data setting inserted"?

You should not be seeing data in the DC with 0 replicas. What does
"data setting inserted" mean?

Do you have sstables on disk with data for the keyspace?

-- 
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)

Re: Cassandra 1.0.6 multi data center question

[Roshan]

Thanks for the reply. But I can see the data setting inserted in DC1 in DC2.
So that means data also getting replicated to DC2. 

Want to know how to restrict this?

--
View this message in context: 
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-1-0-6-multi-data-center-question-tp7268026p7268185.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at 
Nabble.com.

Re: Cassandra 1.0.6 multi data center question

[Peter Schuller]

It is expected that the schema is replicated everywhere, but *data*
won't be in the DC with 0 replicas.

-- 
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)

Re: Cassandra 1.0.6 multi data center question

[Roshan]

I have create the Keyspace like below, but the result is same. All the data
getting replicated to all over the cluster instead of DC1.

create keyspace WSDC
with placement_strategy =
'org.apache.cassandra.locator.NetworkTopologyStrategy' and strategy_options
= {DC1:1,DC2:0};

--
View this message in context: 
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-1-0-6-multi-data-center-question-tp7268026p7268138.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at 
Nabble.com.