nodetool rebuild data size

Hi there, if we have a Cassandra DC1 with data size 60T,RF=3,then we rebuild a new DC2(RF=3),how much data will stream to DC2?20T or 60T? Thanks, Peng Xiao

Re: Batch : Isolation and Atomicity for same partition on multiple table

Entry point is here: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/cql3/statements/BatchStatement.java#L346 , which will call through to https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/service/StorageProxy.java#L938-L953 I believe the

Re: Batch : Isolation and Atomicity for same partition on multiple table

Hi Nicolas, Thanks for you answer. Is your assumption 100% sure ? Because the few test I did - using nodetools getendpoints - shown that the data for the two tables when I used the same partition key went to the same "nodes" . So I would have expected cassandra to be smart enough to apply them in

Re: Deleted data comes back on node decommission

Did you run cleanup before you shrank the cluster? -- Jeff Jirsa > On Dec 13, 2017, at 4:49 AM, Python_Max wrote: > > Hello. > > I have a situation similar to > https://issues.apache.org/jira/browse/CASSANDRA-13153 except mine cassandra > is 3.11.1 (that issue

Deleted data comes back on node decommission

Hello. I have a situation similar to https://issues.apache.org/jira/browse/CASSANDRA-13153 except mine cassandra is 3.11.1 (that issue should be fixed according to jira). Cluster consist of 40 nodes which I have to shrink to 25 more powerful nodes moving less powerful out from the cluster.

Re: Batch : Isolation and Atomicity for same partition on multiple table

Hi Mickael, Partition are related to the table they exist in, so in your case, you are targeting 2 partitions in 2 different tables. Therefore, IMHO, you will only get atomicity using your batch statement On 11 December 2017 at 15:59, Mickael Delanoë wrote: > Hello, > > I