You can administer clusters from OpsCenter:
OpsCenter Enterprise Edition 3.0 can monitor and administer Cassandra 1.2 as described in these procedures unless you enable virtual nodes. When you enable virtual nodes, OpsCenter chooses a single token for each node for operations, such as collecting metrics. Attempting to move nodes, rebalance nodes, and perform other tasks involving token ranges is not supported.
You must have a running and properly configured Cassandra cluster, as described in the documentation. OpsCenter supports:
|OpsCenter versions||Cassandra versions||DSE versions|
|1.4.x||0.7, 0.8, 1.0, 1.1||1.0, 2.0|
|2.0||0.8, 1.0, 1.1||1.0, 2.0|
|2.1||0.8, 1.0, 1.1||1.0, 2.0|
|3.0||1.0, 1.1, 1.2||1.0, 2.x, 3.0|
|3.1||1.0, 1.1, 1.2||1.0, 2.x, 3.0|
|3.2||1.1, 1.2||2.x, 3.0.x, 3.1.x|
You can provision new clusters on colocated hosts or in the cloud.
To create a cluster:
When deploying to EC2, the opscenterd to agent communication must be open to 0.0.0.0 in the EC2 security group (that is for ports 61620 and 61621).
To add a cluster to Opscenter:
Click Add a cluster.
Enter at least one hostname or IP address, newline-delimited, for the nodes comprising the cluster. OpsCenter discovers the other nodes for you.
It is recommended that you supply two or three hosts or IP addresses, in case a given node is down or decommissioned.
If you are not using the default JMX or Thrift ports, enter the appropriate port numbers.
If required, click Add Credentials and enter the username and password for JMX or Thrift ports.
Click Add Cluster.
To generate a PDF report about the cluster being monitored, click Report at the top of the OpsCenter interface. The report shows the version of OpsCenter, number of clusters and nodes being monitoring, gigabytes of storage used, name of the cluster, and information about nodes in the cluster. The node information includes:
You can save or print the PDF report.
You can click Diagnostics to download a tarball that contains information about opscenterd and all nodes in a specified cluster. This can be used to attach to support tickets.
To add a node to a cluster
|Package||The version of DSE to install on the node.|
|DataStax Credentials||The username and password you received when registering to Download DSE.|
|Nodes||The hostname or IP address, token, and software to install on the node (from Cassandra, Solr, and Hadoop). You can add more than one node by clicking Add.|
|Node Credentials (sudo)||The username and password to authenticate on the host. (Optional) the private SSH key to use to use for authentication.|
You can manage cassandra.yaml from OpsCenter. If the cluster exists in multiple datacenters, you can configure cassandra.yaml for a single datacenter, or for all nodes in a cluster. To manage cassandra.yaml for a single node by clicking on the Actions dropdown for a node.
To configure a cluster:
To remove a cluster
This removes the cluster from OpsCenter; it does not delete the cluster.
When you delete a cluster, any EC2 nodes are not deleted.
Cluster rebalancing is a process that makes sure each node in a Cassandra cluster is managing an equal amount of data. Currently, OpsCenter only supports rebalancing on clusters using the random partitioner or murmur 3 partitioner. Ordered partitioners are not supported. When using the random partitioner or murmur 3 partitioner, a rebalance is usually required only when you have changed the cluster topology in some way, such as adding or removing nodes or changing the replica placement strategy.
A cluster is considered balanced when each node is responsible for an equal range of data. This is done by evaluating the partitioner tokens assigned to each node to make sure that the data ranges each node is responsible for are even. Even though a cluster is considered balanced, it is still possible that one or more nodes have more data than the others. This is because the size of the rows is not taken into account, only the number of rows managed by each node.
To rebalance a cluster:
You can start, stop, or restart the Cassandra or DSE service on any node. This can be done via the Actions dropdown on a node.
To restart a cluster:
There is also rolling restart functionality for the entire cluster. This can be done via the "Restart Cluster" in any of the Cluster views.
To modify a cluster setting:
Click Edit Cluster.
Change the IP addresses of cluster nodes.
Change JMX and Thrift listen port numbers. Click Add credentials if the ports require authentication.
(Optional) You can check thhe DSE security (kerberos) is enabled on my cluster and enter the service name.
(Optional) You can check the Client node encryption is enabled on my cluster and enter the CA Certificate File Path.
(Optional) You can check the Validate SSL Certifcates and enter the Truststore File Path and Trustore Password.
For more information about enablinb Kerbeos see Security in the DSE Documentation.
7.Click Save Cluster.