cassandra centos

cassandra.sh

java --version
cqlsh
show VERSION

SELECT cql_version FROM system.local;

nodetool version

select peer, release_version from system.peers;

select release_version from system.local;

bin/cassandra -v

/usr/sbin/cassandra -v

systemctl daemon-reload
systemctl restart cassandra
systemctl enable cassandra
nodetool status

./bin/cassandra -f


Upgrade:

cd /opt/db/cassandra-2212/cassandra/bin
./cassandra


cd /opt/db/cassandra-2212/cassandra/bin
./nodetool upgradesstables

Run nodetool repair

cd /opt/db/cassandra-2212/cassandra/bin
./nodetool repair


https://docs.axway.com/bundle/axway-open-docs/page/docs/apim_installation/apigw_upgrade/upgrade_cassandra/index.html


Best practice
We recommend the following when upgrading your Apache Cassandra version:

Upgrade your API Gateway installation after upgrading your Apache Cassandra version.
In multi-datacenter clusters, upgrade every node in one datacenter before upgrading another datacenter. Upgrade and restart the nodes one at a time. Other nodes in the cluster continue to operate at the earlier version until all nodes are upgraded.
When upgrading a cluster on a single-datacenter or multi-datacenter setup, you must avoid any schema changes until the entire cluster has been upgraded to the same version.
Running nodetool repair on a Cassandra node will affect performance on a system running live traffic. It is recommended that you perform the Cassandra upgrade in the evening or during a maintenance window when the load is minimal.