Re: Creating a copy of a C* cluster

The most effective way to "divorce" it is to remove connectivity between the datacentres. I would put in place firewall rules between the DC's to stop them from communicating, and then rolling restart one of the DC's. You should be left with 2 datacentres that see each other as down, and on each

Re: Cassandra upgrade from 2.2.8 to 3.10

Use 3.11.0, instead of 3.10 too - has bug fixes on top of 3.10 and gets long term release support. -- Michael On 08/07/2017 05:09 PM, Jeff Jirsa wrote: > Cant really stream cross-version. You need to add nodes and then upgrade > them (or upgrade all the nodes, and then add new ones). > > > On

Re: Cassandra upgrade from 2.2.8 to 3.10

Cant really stream cross-version. You need to add nodes and then upgrade them (or upgrade all the nodes, and then add new ones). On Mon, Aug 7, 2017 at 2:58 PM, ZAIDI, ASAD A wrote: > Hi folks, I’ve question on upgrade method I’m thinking to execute. > > > > I’m planning from

Cassandra upgrade from 2.2.8 to 3.10

Hi folks, I’ve question on upgrade method I’m thinking to execute. I’m planning from apache-Cassandra 2.2.8 to release 3.10. My Cassandra cluster is configured like one rack with two Datacenters like: 1. DC1 has 4 nodes 2. DC2 has 16 nodes We’re adding another 12 nodes and would

Re: Creating a copy of a C* cluster

For minimum disruption to your production cluster, restoring from backups is probably the best option. However, there is no reason adding a DC, building and then splitting shouldn’t work if done correct. Cheers Ben On Tue, 8 Aug 2017 at 07:11 Robert Wille wrote: > We need to

Re: Different data size between datacenters

Keyspace has WITH replication = {'class': 'NetworkTopologyStrategy', 'DC1': '3', 'us-east-productiondata': '3'} AND durable_writes = true; From: Jeff Jirsa Reply-To: "user@cassandra.apache.org" Date: Monday, August 7, 2017 at 2:51 PM To: cassandra

Creating a copy of a C* cluster

We need to make a copy of a cluster. We’re going to do some testing against the copy and then discard it. What’s the best way of doing that? I created another datacenter, and then have tried to divorce it from the original datacenter, but have had troubles doing so. Suggestions? Thanks in

Re: Different data size between datacenters

Tombstones should eventually compact away in most cases, but if you've recently changed topology (added nodes, removed nodes, etc), you should run "nodetool cleanup" to remove no-longer-owned data (start by running it on one instance at a time, it's a form of compaction and can impact disk space

Re: Different data size between datacenters

Yes it’s the total size. Could it be that tombstones or data that nodes no longer own is not being copied/streamed to the data center in AWS? From: Jeff Jirsa Reply-To: "user@cassandra.apache.org" Date: Monday, August 7, 2017 at 2:51 PM To:

Re: Different data size between datacenters

And when you say the data size is smaller, you mean per node? Or sum of all nodes in the datacenter? With 185 hosts in AWS vs 135 in your DC, I would expect your DC hosts to have 30% less data per host than AWS. If instead they have twice as much, it sounds like it's balancing by # of tokens

Re: Different data size between datacenters

So we have the default 256 in our datacenter and 128 in AWS. From: "ZAIDI, ASAD A" Reply-To: "user@cassandra.apache.org" Date: Monday, August 7, 2017 at 1:36 PM To: "user@cassandra.apache.org" Subject: RE: Different data

Re: Different data size between datacenters

Yes to the NetworkTopologyStrategy. From: Jeff Jirsa Reply-To: "user@cassandra.apache.org" Date: Monday, August 7, 2017 at 2:39 PM To: cassandra Subject: Re: Different data size between datacenters You're using

Re: Different data size between datacenters

You're using NetworkTopologyStrategy and not SimpleStrategy, correct? On Mon, Aug 7, 2017 at 11:50 AM, Chuck Reynolds wrote: > I have a cluster that spans two datacenters running Cassandra 2.1.12. 135 > nodes in my data center and about 185 in AWS. > > > > The size of

RE: Different data size between datacenters

Are you using same number of token/vnodes in both data centers? From: Chuck Reynolds [mailto:creyno...@ancestry.com] Sent: Monday, August 07, 2017 1:51 PM To: user@cassandra.apache.org Subject: Different data size between datacenters I have a cluster that spans two datacenters running Cassandra

Different data size between datacenters

I have a cluster that spans two datacenters running Cassandra 2.1.12. 135 nodes in my data center and about 185 in AWS. The size of the second data center (AWS) is quite a bit smaller. Replication is the same in both datacenters. Is there a logical explanation for this? thanks