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

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.

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?

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

We met OpsCenter agent out of memory issue before and increased -Xmx in datastax-agent-env.sh to 2048M according to Datastax doc. It has been running well for past few month, recently two agents has out of memory issue again, during running cleanup outdated backup files. Could we increase -Xmx again? Maybe change it to 3072M? Thanks