I have been having a tough time in trying to understand the actual difference between the different ways to start Cassandra on a LINUX Host and how it affects the nodes being visible to each other. I have a 3 node cluster and all the 3 nodes are up and running. There are multiple admins on our team and everyone is using their own ways to start the cassandra on a node. I am wondering if that has any bad effect on the node visibility to each other and other cluster performance issues. When I see that there are multiple ways to start cassandra:
1. Start cassandra from the bin directory (as a stand-alone process)
2. Start Cassandra as a Service option1
sudo service cassandra start
3. Start Cassandra as a Service option2
sudo systemctl start cassandra
What is the difference between the 3 options? How do they vary in the behavior of the nodes?
Also, how to find out which option was used to start it?I don't know what command was used to start the cassandra on this particular node, but as you can see below, it says Cassandra is stopped in 1 command, and that it is active and running in another command. What might be the issue here?
[root@host1 bin]# sudo service cassandra status Cassandra is stopped.
[root@host1 bin]# sudo systemctl status cassandra cassandra.service - LSB: Apache Cassandra database server Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled) Active: active (running) since Sat 2021-04-03 05:07:38 UTC; 3 days ago
Please help as this is issue is really confusing me and I am not able to understand how to proceed further?