Inside OpsCenter 3.0 – Starting, Stopping, Configuring
One of the great features included in OpsCenter 3.0 is Enterprise Provisioning. A very important subset of that feature is the ability to manage the database process and configuration on each node in your cluster. OpsCenter 3.0 gives you the ability to do all of this easily, and in a visual way (or via our API).
Starting and Stopping DataStax Enterprise (DSE)/Cassandra
There are many reasons you may want to start, stop, or even restart the DSE process on a node. OpsCenter now gives you a simple, visual alternative to the command line for doing so. Simply choose one of the options from the Actions dropdown, and let OpsCenter do its thing:
When starting a node, OpsCenter will verify that it has thrift connectivity before reporting success. In the case of restart, OpsCenter ensures the process has stopped successfully before starting it up again.
While being able to manage the DSE process on a single node is great, most practical use cases require restarting the process on multiple nodes. Whether you’ve made a configuration change, or upgraded DSE on each node in your cluster, you can now restart all of those nodes in a rolling fashion with the click of a button.
OpsCenter carefully chooses the order to restart each node, to avoid restarting neighboring nodes when possible. This will give the restarted node a chance to warm up its cache, and prevent performance degradation when clients access data within the ranges that node is responsible for.
You can also configure a delay between restarting nodes, to give each node extra time to get up to speed before restarting the next node.
OpsCenter will ensure each node has started successfully before moving on to the next, and will let you know once the whole cluster has been successfully restarted.
There are a few files involved when configuring a DSE cluster, but the primary file is cassandra.yaml. Up until now, the process for updating settings within cassandra.yaml has been to manually edit each file (IP addresses in the files prevent simple scp), and restart the DSE process on each node one by one. Now with OpsCenter, you can do all of this with the click of a button.
You can choose to modify settings on every node in your cluster or a single datacenter, if you have nodes in multiple datacenters.
OpsCenter will display a pre populated form, with fields relevant to your version of DSE.
Once OpsCenter has pushed the changes to each node, you have the option to easily perform a rolling restart, as described above. A restart is needed for the changes to take effect.
OpsCenter’s purpose in life is to make managing and maintaining your DSE clusters as easy as possible, and the features mentioned here are a big step in achieving that. If you have any questions, comments, or want to let us know some of the things you’d like OpsCenter to make easier for you, don’t hesitate to let us know in the comments, or via the “Feedback” link in the OpsCenter UI.