Load discrepancy between old vs new nodes of Cassandra

Hi, We are using Cassandra 3.0.13 We have the following datacenters: - DC1 with 7 Cassandra nodes with RF:3 (2 years old) - DC2 with 1 Cassandra node with RF:1 (4 years old) - DC3 with 2 Cassandra nodes with RF:2 (one-month-old) On DC2 and DC3, each node has 100% data. Seed nodes while

Encrypting JMX password for cassandra

Hello, When enabling JMX Authentication , username and password are stored as plain text in jmxremote.password file. Is there a way to encrypt the content of this file so it's not human readable?

Re: Load discrepancy between old vs new nodes of Cassandra

I would start by checking the replication settings on all your keyspaces. There's a chance that you have keyspaces not replicated to DC3. FWIW it would have to be an application keyspace (vs system keyspaces) because of the size. Cheers!

Re: Encrypting JMX password for cassandra

No, there isn't. You can either set the permissions to 400 so only the OS cassandra user can read the file or enable internal C* auth so the password is not stored in a file. Cheers!

Re: Encrypting JMX password for cassandra

Thanks Erick Can you please point me the doc for internal c* auth? Are you referring to c* auth for jmx? On Monday, August 17, 2020, Erick Ramirez wrote: > No, there isn't. You can either set the permissions to 400 so only the OS > cassandra user can read the file or enable internal C* auth so

Re: Encrypting JMX password for cassandra

That's correct. The instructions are in the document you already linked plus in the official docs[1] on the Apache website. Cheers! [1] https://cassandra.apache.org/doc/latest/operating/security.html#jmx-access >

Repeated messages about Removing tokens

Hello, I am trying to add and decommission some nodes into the cluster. While some nodes are decommissioned I see the below error messages repeatedly on the rest of C* nodes logs. It's not for all the IPs but for a few of them. Is this an issue? INFO [GossipStage:7] 2020-08-18 04:22:07,168 Stora