Impact analysis of upgrading RHEL/SLES OS

Hi All, I am running Cassandra 3.11.2 on RHEL 7.4. I am planning for an OS upgrade from RHEL 7.4 to RHEL 7.9/8.x and SLES15. But I could not find any relevant information on the impact of upgrading an OS. Could you share any reference or your analysis of these impacts? I would appreciate it if yo

How to restore single Kubernetes node?

Hi All, In standard deployment (VM), I backup & restore a single Cassandra node. I am exploring how I can restore a pod in the Kubernetes cluster but I could not find any relevant information. Please share your thoughts/views on how this should be done in Kubernetes. Any reference or pointer is h

how to choose tombstone_failure_threshold value if I want to delete billions of entries?

Hi Team, I have a table having approx 15 billions entries and I want to delete approx 13 billions entries from it. I cannot write 13 billion tombstones in one go since there is a disk space crunch. I am planning to delete data in chunks so I will be creating 400 millions tombstones in one go. No

Issue with anti-compaction while running full repair with -pr option

Hi Team, In Cassandra 3.x, Anti-compaction is performed after repair (incremental or full). Repair does not have any way to bypass anti-compaction (if not running sub range repair with -st & -et). Here is a jira ticket. https://issues.apache.org/jira/browse/CASSANDRA-11511 I am facing 100% disk

Re: Getting Invalid Yaml exception after we upgraded java version

Update : We also upgraded the Cassandra version from 2.1.16 to 3.11.2. On Fri, Aug 21, 2020 at 9:02 AM Pushpendra Rajpoot < pushpendra.nh.rajp...@gmail.com> wrote: > Hi, > > We have updated the java minor version as given below. > > Older Java version "1.8.0_144"

Getting Invalid Yaml exception after we upgraded java version

Hi, We have updated the java minor version as given below. Older Java version "1.8.0_144" Newer Java version "1.8.0_261" Cassandra version : 2.1.16 Now we are getting below exception : INFO [main] 2020-08-19 10:55:09,364 YamlConfigurationLoader.java:89 - Configuration location: file:/etc/cass

Corrupt SSTable

Hi, I have a cluster of 2 DC, each DC has 5 nodes in production. This cluster is based on active-passive model i.e. application is writing data on one DC (Active) & it's replicated to other DC (Passive). My Passive DC has corrupt sstables (3 nodes out of 5 nodes) whereas there are no corrupt ssta

Re: Connect java application to Cassandra in Kubernetes

addContactPoints(*IntetAddress.getAllByName*(headlessService)); >> >> getAllByName will return all of the endpoints. If the entire C* cluster >> goes down, you will need to bounce the driver. >> >> Cheers >> >> John >> >> On Thu, Aug 6, 2020 at

Connect java application to Cassandra in Kubernetes

We have created a statefulset & headless service to deploy Cassandra in Kubernetes. Our client is also in the same Kubernetes cluster. We have identified two ways by which we can find contact point for driver in client application: 1. Use 'cassandra-headless-service-name' as contactPoints 2.

Connect java application to Cassandra in Kubernetes

We have created a statefulset & headless service to deploy Cassandra in Kubernetes. Our client is also in the same Kubernetes cluster. We have identified two ways by which we can find contact point for driver in client application: 1. Use 'cassandra-headless-service-name' as contactPoints 2.