What are the steps (or all the commands) to upgrade (just the 6.8.25 fix, I have 6.18.16 version now) all nodes in cluster with LifeCycle Manager? I've found this but it refers to 6.5 version of DSE: https://docs.datastax.com/eol/en/opscenter/6.5/opsc/LCM/upgradeDSEjob.html

I would like to use these two pages to enable DSE Unified Authentication and realize a secure environment. I have tried to configure it but it does not work. How is it as a symptom. When I type nodetool -u -pw status I get

"nodetool: Failed to connect to '127.0.0.1:7199' - FailedLoginException: 'Failed to login. Please re-try.'."

is returned. 2. nodetool status command from node2, which has not touched any files related to DSE Unified Authentication from the initial state, confirms that node1 is working as usual. Please let me know if you have any other suggestions on what else I should try or if I should change a file here or there. If I hit nodetool -h drain, etc. from another node, I get an error, but it is not an Error about Authentication, but a ConnectException. DOCUMENTS https://docs.datastax.com/en/dse68-security/docs/Auth/secEnableDseAuthenticator.html https://docs.datastax.com/en/dse68-security/docs/secJmxAuth.html Enabling JMX Native Authentication. procedure is not implemented.

The previous DBA created and connected a cluster (4 nodes) to DSE OpsCenter. It's almost perfect (nodes are connected and visible) except for the STOMP service. In the OpsCenter -> Nodes -> Agents there are question marks in the STOMP service column. What should I check first? The firewall seems to be ok, like in the other 3 clusters, which work perfectly fine.

Im preparing to upgrade my Cassandra cluster (3 Nodes x 2 DCs) from Cassandra 3.0.15 to 4.1.4, when i tried the upgradation process in a similar setup i faced following issues in the middle of the rolling upgrade. **0) Schema version mismatch:** Cluster status --> DC1 : ( 1 x 4.1.4 ) + ( 2 x 3.0.15 ) && DC2 : 3 x 3.0.15 Schema versions: (Its not an issue) 77876dfb-de1f-3826-89b2-ff6d502bcd6c: [C* 3.0.15 node ips] 018b628e-98aa-36f4-9e7e-a40cca8bc44d: [C* 4.1.4 node ip] ***1) ReadTimeoutException from client*** Cluster status --> DC1 : ( 1 x 4.1.4 ) + ( 2 x 3.0.15 ) && DC2 : 3 x 3.0.15 Caused by: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency LOCAL_QUORUM (2 responses were required but only 1 replica responded) Above issue happened when i tried query configuring Cassandra 4.1.4 node as the coordinator node. Query succeeded only after reduced the consistency to LOCAL_ONE. **Things worked smoothly when all the nodes are Cassandra 3.0.15, so there is no network latency.** **2) ReadTimeout from CQLSH** Cluster status --> DC1 : ( 1 x 4.1.4 ) + ( 2 x 3.0.15 ) && DC2 : 3 x 3.0.15 ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting for replica nodes' responses] message="Operation timed out - received only 0 responses." info={'consistency': 'ONE', 'required_responses': 1, 'received_responses': 0} Inconsistently getting above exception when executing query from in the CQL SHELL of the nodes of the DC with mixed versions of Cassandra. > ***Note :*** I tried query(SELECT *) a table which has replication factor of 2 via CQL SHELL of each node, I observed that I'm getting > above exception from Cassandra 3.0.15 nodes alone not from Cassandra > 4.1.4 node. **3) UnauthorizedException** Cluster status --> DC1 : ( 1 x 4.1.4 ) + ( 2 x 3.0.15 ) && DC2 : 3 x 3.0.15 Caused by: com.datastax.driver.core.exceptions.UnauthorizedException: Unable to perform authorization of super-user permission: Operation timed out - received only 1 responses.

Is there any way to enforce password policy for Cassandra database users? Something like the password must contains 8 characters with a special character , an upper case character and a lower case. FYI, we are on Datastax Cassandra latest version.

I have a question about Cassandra Backup & Restore procedure. I have setup a 3-node source cluster and now I took a backup of a keyspace using: https://docs.datastax.com/en/dse/6.8/dse-admin/datastax_enterprise/operations/opsBackupRestoreManaging.html Now I copied all the backups from three nodes and trying to restore on the target 3-node Cassandra cluster using: https://docs.datastax.com/en/dse/6.8/dse-admin/datastax_enterprise/operations/opsBackupRestoreRestoring.html But it doesn't allow us to restore keyspace from the different cluster, could you please direct or recommend how I can create a copy or clone of source cluster?

Our Cassandra cluster has 21 nodes and each node is set **num_token=16**. From my understanding, the token range is between -263 to +263-1, each partition key is hashed (MurMur3 hash function) to a token within this range. We thought the token range for each vnode would be **(-263 to +263-1)/num** of vnode (in this case 21x16, totally 336 vnodes). so the sum of token range for each node would be 4.7%. When we check on nodetool ring and calculated the sum as follow: As shown above the percentage varies from 3 to 6%. Is there a way to make the token range distributed more evenly across all the nodes? We are seeing uneven disk usage in this cluster likely cause by this. Any suggestion would help.

Using datastax-java-driver-core 4.13.0 to connect the Java application to Cassandra. When a Cassandra node goes down, all in-flight requests to that node fail with a DriverTimeoutException. This exception is not handled by DefaultRetryPolicy, meaning no automatic retry happens. The requests are non-idempotent, so implementing a custom retry mechanism risks duplicate writes. **Questions:** How can we gracefully handle DriverTimeoutException without causing duplicate writes? Is there a recommended way to retry only safe operations in such scenarios while preventing data inconsistency? Are there any DataStax-recommended strategies to mitigate request failures when nodes go down? Any guidance or best practices would be greatly appreciated!

Is there any DSE 6.x version supporting C* 4.x sstable format (-nb-)? I want to load data from apache C* 4.x using sstableloader into DSE 6.x. What would be the best recommended upgrade path (compatible) to import C* 4.x sstables into DSE 6.x? - DSE 6.x - protocol DSE_V2 - (sstable format -bb-) - C* 4.x - protocol v5 - (sstable format -nb-) Using Apache Cassandra 4.x sstableloader -> The client is unable to negotiate a protocol even after adding application.conf (v4) in EXTRA_CLASSPATH as per doc . Error remains same irrespective of any provided compatible driver:

com.datastax.driver.core.exceptions.UnsupportedProtocolVersionException: \
  [/10.x.x.x:9042] Host does not support protocol version V6 but V5.

Using DSE 6.8.x sstableloader -> Import of -nb- sstables from 4.x complete without errors but there are no files in /data path of DSE cluster and SELECT * from TABLE returns 0 rows. Using nodetool refresh and nodetool import doesn't seem to help. There is no clear information of C* 4.x compatibility with DSE on Datastax documentation. Any links or information around this would be helpful. Thanks!

I started the spark by dse spark command. Later I created a one rdd with cassandra keyspace and table .. Trying to print contents of tables using rddname.first But it shows couldn’t able to find keyspace or tables

I can't perform an upgrade to the latest version of DSE via Lifecycle Manager. Specifically, it's that I can't point to a version higher than 6.8.43 (that's also the current version used on nodes). Both on the server with OpsCenter and on all hosts to be upgraded there are DSE packages version 6.8.47 available in the repo. yum search all dse --showduplicate | grep "6.8.47" dse-6.8.47-1.noarch : This package contains the full dse distribution. dse-demos-6.8.47-1.noarch : This package contains the dse demo applications. dse-full-6.8.47-1.noarch : This package contains the full dse distribution. dse-libgraph-6.8.47-1.noarch : This package contains the dse graph libraries. dse-libspark-6.8.47-1.noarch : This package contains the dse spark libraries. dse-libcassandra-6.8.47-1.noarch : This package contains the dse cassandra libraries. dse-libhadoop2-client-6.8.47-1.noarch : This package contains the dse hadoop 2 (client) libraries. dse-liblog4j-6.8.47-1.noarch : This package contains the dse log4j libraries. dse-libsolr-6.8.47-1.noarch : This package contains the dse solr libraries. dse-libtomcat-6.8.47-1.noarch : This package contains the dse tomcat libraries. Until recently, it worked seamlessly. Now it's like this: What is the problem?

We have 48 Nodes Cassandra Cluster and we are getting a repeated error in only one node.Any idea what may be the reason. Error is as below :

ERROR [BatchlogTasks:1] 2023-08-29 09:12:55,524  CassandraDaemon.java:139 - Exception in thread Thread[BatchlogTasks:1,5,main]
java.lang.NullPointerException: null
        at org.apache.cassandra.batchlog.BatchlogManager$ReplayingBatch.(BatchlogManager.java:367)
        at org.apache.cassandra.batchlog.BatchlogManager.lambda$processBatchlogEntries$0(BatchlogManager.java:290)
        at org.apache.cassandra.utils.flow.Flow$ReduceSubscriber.onNext(Flow.java:1227)
        at org.apache.cassandra.utils.flow.Threads$SchedulingTransformer.lambda$onNext$0(Threads.java:326)
        at org.apache.cassandra.concurrent.TPCRunnable.run(TPCRunnable.java:101)
        at org.apache.cassandra.concurrent.IOScheduler$PooledTaskWorker.run(IOScheduler.java:319)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.lang.Thread.run(Thread.java:748)
        at org.apache.cassandra.utils.concurrent.InlinedThreadLocalThread.run(InlinedThreadLocalThread.java:251)
        at org.apache.cassandra.concurrent.IOThread.run(IOThread.java:46)
        Suppressed: org.apache.cassandra.utils.flow.Flow$FlowException: Flow call chain:
        PagerFlow
        SchedulingTransformerIO scheduler: cached workers: 7(IOScheduler.java:183)
        ReduceToSingle      org.apache.cassandra.batchlog.BatchlogManager$$Lambda$2231/914170156@7b2cb757(BatchlogManager.java:286)
                at org.apache.cassandra.utils.flow.Flow.wrapException(Flow.java:2683)
                at org.apache.cassandra.utils.flow.Flow$ReduceSubscriber.onError(Flow.java:1270)
                at org.apache.cassandra.utils.flow.Flow$ReduceSubscriber.onNext(Flow.java:1231)
                ... 13 common frames omitted

I am trying to restore backups generated by OpsCenter on target cluster with different topology using sstableloader but sstableloader is not able to recognize backups taken by OpsCenter. There are no errors but files are not streamed. sstableloader -d 127.0.0.1,127.0.0.2,127.0.0.3 -v /backup/killrvideo/videos -u cassandra -pw xxxxxxxx WARN 20:10:37,677 Only 51.247GiB free across all data volumes. Consider adding more capacity to your cluster or removing obsolete snapshots Established connection to initial hosts Opening sstables and calculating sections to stream Summary statistics: Connections per host : 1 Total files transferred : 0 Total bytes transferred : 0.000KiB Total duration : 5420 ms Average transfer rate : 0.000KiB/s Peak transfer rate : 0.000KiB/s /backup/killrvideo/videos folder has sstables files related to killrvideo.videos. File names were extracted from backup.json file Next I tried to take backup using nodetool snapshot of same table. I coped files from snapshot folder of [data]/killrvideo/videos to my backup folder /backup/killrvideo/videos and then executed same sstableloader command and this time it was successful. Does that mean backups taken by opscenter are not compatible with sstableloader ? What am I missing ? How to load backups of opscenter using command line sstableloader ? sstableloader is from default location of datastax-dse installation : resources/cassandra/bin/sstableloader DataStax Version : 6.8.25 Please advice.

DataStax OpsCenter for Cassandra - why is disk usage reported by storage capacity widget different than "Data Size" metric? The Storage Capacity widget shows 38.96 TB used but a graph of the "Data Size" (data-load) metric (for the "cluster wide") shows 14.30 TB used. This cluster has two data centers and a RF of 3 for all tables. Here is an example image of the Storage Capacity widget

The user I'm referring to is the user created by the Datastax DSE package install. I'd like to replace that user with another account. I've found a couple of places where the "Cassandra user" is defined, in the init.d file as well as in the /default/DSE directory. I've also already reassigned permissions from "Cassandra" to my new user, but the DSE service won't start up unless I run it as **root** now. I've gone as far as completely wiping out the data, removing the node from the cluster, and repairing it with nodetool, but I can still only run the service as **root** or change everything back to the "Cassandra" user. The error message states that it's a read error in the metadata directory, but I've already ensured that the account has rights to it as well as the parent, I've also cleared out the local and peers file that was in the metadata directory.

We are using Cassandra for our services with a cluster of 4 data center and 6 nodes in each DC. Recently we update our node SKU by first adding 6 new nodes in same data center, migrating the data from existing nodes to new nodes and then removed old nodes by running either nodetool decommission or nodetool removenode command. After this we started seeing that new Cassandra nodes are frequently going down and throwing error A node with address already exists, cancelling join while trying to come up. It then doesnt come up. I need to remove the node which is in DN status and restart Cassandra service again to make this node up. But after few days same thing happens again. Wondering why we started seeing this issue suddenly and how can this be fixed. We are using Apache Cassandra 3.11.10 version. Error logs : `ERROR [main] 2023-04-17 17:28:29,128 CassandraDaemon.java:803 - Exception encountered during startup java.lang.RuntimeException: A node with address DM3PEPF00014567/10.115.155.147 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node.     at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:632) ~[apache-cassandra-3.11.10.jar:3.11.10]     at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:880) ~[apache-cassandra-3.11.10.jar:3.11.10]     at org.apache.cassandra.service.StorageService.initServer(StorageService.java:738) ~[apache-cassandra-3.11.10.jar:3.11.10]     at org.apache.cassandra.service.StorageService.initServer(StorageService.java:687) ~[apache-cassandra-3.11.10.jar:3.11.10]     at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:395) [apache-cassandra-3.11.10.jar:3.11.10]     at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:633) [apache-cassandra-3.11.10.jar:3.11.10]     at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:786) [apache-cassandra-3.11.10.jar:3.11.10]` This node was up and running for last few months and suddenly started throwing this error. I can confirm that node with same IP address doesnt exists in cluster. Here is the nodetool status for this DC : When this happens I usually run nodetool removenode command which will remove this node and then restart Cassandra on that cluster which will bring it up. But wondeirng how to fix this issue permanently as we are seeing this very intermittently.

i am trying to start Apache Cassandra 3.11.2 on Centos 7 and i get error

Exception (org.apache.cassandra.exceptions.ConfigurationException) encountered during startup: Unable to find authenticator class 'com.datastax.bdp.cassandra.auth.PasswordAuthenticator'
Caused by: java.lang.ClassNotFoundException: com.datastax.bdp.cassandra.auth.PasswordAuthenticator
        at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:264)
        at org.apache.cassandra.utils.FBUtilities.classForName(FBUtilities.java:556)
        ... 8 more
ERROR [main] 2023-02-21 14:22:24,788 CassandraDaemon.java:803 - Exception encountered during startup
org.apache.cassandra.exceptions.ConfigurationException: Unable to find authenticator class 'com.datastax.bdp.cassandra.auth.PasswordAuthenticator'
        at org.apache.cassandra.utils.FBUtilities.classForName(FBUtilities.java:560)
        at org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:593)
        at org.apache.cassandra.utils.FBUtilities.newAuthenticator(FBUtilities.java:536)
        at org.apache.cassandra.auth.AuthConfig.applyAuth(AuthConfig.java:53)
        at org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(DatabaseDescriptor.java:154)
        at org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(DatabaseDescriptor.java:137)
        at org.apache.cassandra.service.CassandraDaemon.applyConfig(CassandraDaemon.java:680)
        at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:622)
        at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:786)
Caused by: java.lang.ClassNotFoundException: com.datastax.bdp.cassandra.auth.PasswordAuthenticator
        at java.net.URLClassLoader.findClass(URLClassLoader.java:387)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:264)
        at org.apache.cassandra.utils.FBUtilities.classForName(FBUtilities.java:556)
        ... 8 common frames omitted

(attached screen)

Getting Gossip error when trying to setup 3 node cluster. 1. Node-1: Private IP: 10.10.0.1 Public IP: public_ip_1 2. Node-2: Private IP: 10.10.0.2 Public IP: public_ip_2 3. Node-3: Private IP: 10.10.0.3 Public IP: public_ip_3 Here you go my cassandra.yaml seeds: '10.10.0.1' listen_address: 10.10.0.1 broadcast_address: public_ip_1 start_native_transport: true native_transport_address: public_ip_1 Error ERROR [DSE main thread] 2023-02-16 09:38:09,271 CassandraDaemon.java:938 - Exception encountered during startup java.lang.RuntimeException: Unable to gossip with any peers Node get shut down

I am attempting to use the root user as the cassandra user but getting an error in the output log: Running Cassandra as root user or group is not recommended - please start Cassandra using a different system user. If you really want to force running Cassandra as root, use -R command line option. I understand what it is saying but I am not starting cassandra from the command line, I am using the "service dse start/stop" where do I add that -R

As stated in the title, I'm wondering what the best way to monitor compaction strategy performance is on my DSE cluster over time, as it (the database) grows. The current strategy in use is leveledCompaction. Any information, input, guides, etc. you can recommend for monitoring strategy are welcome.