DataStax OpsCenter offers features to more easily manage both DataStax Enterprise and Apache Cassandra clusters.

Basic architecture diagram and explanation.

Installation options include instructions for standalone installers, packages, and tarball installs.

DataStax agents must be installed on every managed node in a cluster and are necessary to perform most of the functionality within OpsCenter.

Default port numbers used by OpsCenter and the DataStax Agents.

File locations can vary based on the type of install.

Commands for starting, stopping, and restarting OpsCenter for each type of installation.

Commands for starting and restarting DataStax agents for each type of installation.

OpsCenter allows enabling user authentication, adding users, and defining custom roles.

OpsCenter uses Secure Socket Layer (SSL) to encrypt the communication protocol and authenticate traffic between DataStax agents and the main OpsCenter daemon. SSL is disabled by default. Enabling SSL is recommended.

Enable Hypertext Transfer Protocol Secure (HTTPS) support in OpsCenter and specify SSL information for better security.

If a cluster uses Kerberos authentication, you need to create and configure the OpsCenter principles before adding the cluster to OpsCenter.

The OpsCenter Event Log page in the Activities section displays a continuously updated list of events and alerts.

OpsCenter collects system and column family metrics data for each node in a cluster.

OpsCenter uses definition files to enable support for different versions of DataStax Enterprise, DataStax Community, and Cassandra without the need to upgrade the currently installed version of OpsCenter itself.

Automatic failover from the primary DataStax OpsCenter instance to the backup OpsCenter instance provides high availability without any manual intervention or downtime.

Configure capabilities by manually modifying the opscenterd.conf, cluster_name.conf, and address.yaml configuration files.

OpsCenter allows starting and stopping the DataStax Enterprise/Cassandra process on each node in a visual manner. Customize the startup or shutdown of a node using the provided example scripts.

Example scenarios of OpsCenter deployments include configuring for multiple regions, IP forwarding, or very large clusters.

Describes the major areas of functionality available in the OpsCenter workspace.

Describes logging in and out of OpsCenter and changing the user password when authentication is enabled.

The New Cluster menu command in OpsCenter allows creating new clusters or managing existing clusters.

In the Cluster section of OpsCenter, select different views of the nodes comprising a Cassandra cluster and then perform node management.

OpsCenter manages multiple DataStax Enterprise or Apache Cassandra clusters with a single install of the central opscenterd server.

Monitor performance metrics in the OpsCenter Dashboard. Real-time and historical performance metrics are available at different granularities: cluster-wide, per node, or per table (column family).

DataStax Enterprise (DSE) comes bundled with enterprise management services that you can configure and run using OpsCenter.

Create and manage keyspaces and the column families within keyspaces.

Increasing the nodelist polling period or setting a sleep delay can reduce excessive CPU usage when starting or running opscenterd.

Set ssl_validate to False if you use a self-signed certificate and experience difficulty connecting to a Cassandra cluster.

Workaround for browser environments where the OpsCenter UI is unable to establish a persistent streaming connection to opscenterd. Another symptom includes the perpetual Loading OpsCenter screen.

Currently supported browsers include Chrome, Firefox, and Safari. IE is not supported at this time.

Instructions to upgrade the OpsCenter snapshot.

For OpsCenter versions prior to 3.2.1, truncate column families to reclaim space.

Upgrade Python if you encounter any difficulty adding a keyspace.

Fix for the error when OpenSSL is installed on Linux distributions.

Resolve the error by compiling Python with SSL support.

Ensure there are no conflicts with port 7199 used by the DataStax Agent.

Limit monitored metrics to conserve disk space.

Error when Java is not installed or the path is not set.

Refer to the recommended settings for insufficient user resource limits errors in the Cassandra documentation.

EPEL is a prerequisite for OpsCenter on CentOS 5.x or RHEL 5.x.

Troubleshooting tips for typical provisioning issues.

Workarounds for sstableloader issues on older versions of Cassandra and DSE.

Change settings in cassandra.yaml to fix a Cassandra connection timeout in OpsCenter.

Add a firewall rule allowing access to port 8888 or disable Web Protection to fix the browser access issue.

Disables the check for the latest versions of OpsCenter and DSE.

Release notes for the OpsCenter version 5.1.4 release.

Release notes for the OpsCenter version 5.1.3 release.

Release notes for the OpsCenter version 5.1.2 release.

Release notes for the OpsCenter version 5.1.1 release.

Release notes for the OpsCenter version 5.1.0 release.