Re: Encryption at rest

2020-06-24 Thread Arvinder Dhillon
Do it at storage level. On Wed, Jun 24, 2020, 1:01 PM Jeff Jirsa wrote: > Not really, no. > > > On Wed, Jun 24, 2020 at 1:00 PM Abdul Patel wrote: > >> Team, >> >> Do we have option in open source to do encryption at rest in cassandra ? >> >

Re: Implication of having similar private IPs in two datacenters

2020-06-24 Thread Erick Ramirez
> > In a network one can assign valid private IP. Private IPs can conflict if > we do not put any restriction on private IP. > Yes, you're right and I was aware of that (not realising that your question was more around what I would consider multi-region comms). My disconnect now is around the

Cassandra write path during the decommissioning process

2020-06-24 Thread Jai Bheemsen Rao Dhanwada
Hello, I would like to understand how the writes happen when there is a node in the cluster that is being decommissioned. During the decommission process, the node will send the streams to the rest of the nodes that it owns. what happened to the read and write of the data that is owned by the

Re: Implication of having similar private IPs in two datacenters

2020-06-24 Thread Jeff Jirsa
So a few things are true: - Cassandra uses IP addresses for internal data structures (in released versions), so duplicating IP nominally means stomping on the wrong host - Cassandra also differentiates broadcast IP from listen IP (local IP) - The broadcast IP is what the other DC is going to

Encryption at rest

2020-06-24 Thread Abdul Patel
Team, Do we have option in open source to do encryption at rest in cassandra ?

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

2020-06-24 Thread Jon Haddad
Generally speaking, don't run mixed versions longer than you have to, and don't upgrade that way. Why? * We don't support it. * We don't even test it. * If you run into trouble and ask for help, the first thing people will tell you is to get all nodes on the same version. Anyone that's doing so

RE: Cassandra upgrade from 3.11.3 -> 3.11.6

2020-06-24 Thread Durity, Sean R
That seems like a lot of unnecessary streaming operations to me. I think someone said that streaming works between these 2 versions. But I would not use this approach. Why not an in-place upgrade? Sean Durity From: Jai Bheemsen Rao Dhanwada Sent: Wednesday, June 24, 2020 11:36 AM To:

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

2020-06-24 Thread Jai Bheemsen Rao Dhanwada
Thank you all for the suggestions. I am not trying to scale up the cluster for capacity but for the upgrade process instead of in place upgrade I am planning to add nodes with 3.11.6 and then decommission the nodes with 3.11.3. On Wednesday, June 24, 2020, Durity, Sean R wrote: > Streaming

RE: Cassandra upgrade from 3.11.3 -> 3.11.6

2020-06-24 Thread Durity, Sean R
Streaming operations (repair/bootstrap) with different file versions is usually a problem. Running a mixed version cluster is fine – for the time you are doing the upgrade. I would not stay on mixed versions for any longer than that. It takes more time, but I separate out the admin tasks so

Re: Implication of having similar private IPs in two datacenters

2020-06-24 Thread manish khandelwal
The nodes within one datacenter will talk on private IPs and for communication across data center public ips are used. Does that answer your question? or you are asking in terms of network layer. As per this link

Empty counter != 0

2020-06-24 Thread Juliusz Stasiewicz
Let's consider a table with two columns of counter type: cqlsh:ks> CREATE TABLE t(p int PRIMARY KEY, c1 COUNTER, c2 COUNTER); cqlsh:ks> UPDATE t SET c1 = c1 + 1 WHERE p = 1; We have one row now: p | c1 | c2---++-- 1 | 1 | null My question is: should we treat the null counter (`c2`

Re: Implication of having similar private IPs in two datacenters

2020-06-24 Thread Erick Ramirez
Putting Cassandra aside, I'm curious to know how you envision that would work from a network perspective. How would the connectivity between servers work? >

Re: Cassandra container, Google Cloud and Kubernetes

2020-06-24 Thread Erick Ramirez
This isn't a direct answer to your questions but you might be interested in the Kubernetes operator for Apache Cassandra [1] from DataStax. You can use the cass-operator to deploy a C* 3.11.6 image to your Kubernetes cluster. The docs are available here [2]. FWIW there are several other published

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

2020-06-24 Thread Erick Ramirez
> > Can I add new nodes with the 3.11.6 version to the cluster running with > 3.11.3? > Technically you can. You'll be able to add 3.11.6 nodes to a 3.11.3 cluster. In fact, the reverse works too in my tests but I personally wouldn't want to do it in production. > Also, I see the SSTable

Re: Cassandra upgrade from 3.11.3 -> 3.11.6

2020-06-24 Thread manish khandelwal
Rightly said by Surbhi, it is not good to scale with mixed versions as debugging issues will be very difficult. Better to upgrade first and then scale. Regards On Wed, Jun 24, 2020 at 11:20 AM Surbhi Gupta wrote: > In case of any issue, it gets very difficult to debug when we have > multiple

Implication of having similar private IPs in two datacenters

2020-06-24 Thread manish khandelwal
Are there any implication if I have similar set of private IPs in two data centers. For example if I have A,B and C as private IPs in one data center and I define A,B and C as my private IPs in other data center, does it impact the cluster? Regards

Cassandra container, Google Cloud and Kubernetes

2020-06-24 Thread Manu Chadha
Hi I want to run Cassandra container in GCP and want to orchestrate the containers using Kubernetes. I have a Cassandra image in my Docker Registry. Following the steps from the following tutorial, I have created a cluster and have Cassandra running on it.