email iconemail phone iconcall



Manikandan Srinivasan, Sr. Director, Products

Announcing DSE OpsCenter 6.1

By Manikandan Srinivasan, Sr. Director, ProductsApril 21, 2017

The latest enhancements for administration and monitoring DataStax Enterprise deployments  

DataStax Enterprise OpsCenter is an easy-to-use visual management and monitoring solution enabling administrators, architects, and developers to quickly provision, monitor, and maintain DataStax Enterprise (DSE) clusters, which includes the best distribution of Apache Cassandra™. Today, I am pleased to announce the general availability of DSE OpsCenter 6.1, fully supporting DataStax Enterprise (DSE) 5.1. Let me provide a quick tour of some of the enhancements found in DSE OpsCenter 6.1

Introduction to DSE OpsCenter

Apache Cassandra has made great strides as a technology since its initial 2008 release, being deployed  by companies to power their mission-critical applications. As we know, with any distributed system, management can be difficult.

DSE OpsCenter is the key piece to the tricky management puzzle. Helping surface critical issues and solving others that you couldn’t see with open source Apache Cassandra. From being notified of best practices, automating backups, or quickly understanding the health of your deployment, the goal of DSE OpsCenter is to make your management and monitoring push-button simple. DSE OpsCenter 6.1 builds onto this goal and pushes it further as you’ll see in this blog.

Enhanced Repair Service

Running repairs consistently across DSE clusters, especially with frequent deletes and updates, is a very critical task.  When you run millions of operations/sec, entropy is inevitable. The DSE OpsCenter Repair Service is configured to run continuously and perform repair operations across a DSE cluster with minimal impact. Repair Service runs in the background, constantly repairing small chunks of a cluster to alleviate the pressure and potential performance impact of having to periodically run repair on entire nodes.

In DSE OpsCenter 6.1, we have made numerous improvements to our existing Repair Service that include:

  • New and improved user experience (Fig 1) to easily view repair progress and identify issues
  • Improved support for incremental repairs
  • Enhanced algorithm to pick efficient parallel repairs paths
  • Heavily optimized subrange repairs
  • Increased resiliency to environmental failures

Fig 1: DSE OpsCenter Repair Service

Improved Backup Service

DSE OpsCenter provides different backup and restore strategies and procedures to protect your database against any data loss. In 6.1, we have added some new features and improvements to ensure that the backup and restore workflows are robust and scalable.

To begin, you can now take a backup at the data center level. This allows for a much more flexible way to run your backups, which will result in decreased storage costs and improved backup and restore speeds. In addition, we have also made improvements to our Amazon S3 backup destination by now natively leveraging Amazon S3 APIs to improve speed and efficiency.

Furthermore, for local destinations, you now have the ability to clone backups between different heterogeneous clusters. In prior versions of DSE OpsCenter, the backup service parsed a file directory of snapshots and put metadata about each file onto a work queue. That queue was then consumed by the snapshot component which sent each file to the appropriate destinations. In DSE OpsCenter 6.1, we moved to a backup job queue which allows us to handle more simultaneous files thus improving the overall backend algorithm.

For more details, refer to our documentation to see all the improvements in the Backup Service.

Agent Backward Compatibility

In DSE OpsCenter 6.1, we greatly reduced the operational complexity of managing your DSE OpsCenter deployment.

To elaborate, the older architecture of DSE OpsCenter required DSE OpsCenter agents to be upgraded and  synchronized with the corresponding DSE OpsCenter server version. This meant that even a minor-subversion upgrade of DSE OpsCenter server resulted in additional complexity for you especially during upgrade cycles.  Starting in DSE OpsCenter 6.1, you will be able to run newer versions of the DSE OpsCenter server with older versions of the agent.  For more details, please refer here.

Fig 2: Agents Backward Compatibility

New DSE Graph Metrics

In this release we added a lot of DSE Graph metrics to enable users to identify the state of their graph objects and quickly identify performance bottlenecks in the clusters. This includes a variety of metrics that includes cache metrics, transaction latencies metrics & graph thread metrics. We will continue to enhance our support for DSE Graph and add many more functionalities in upcoming releases to improve the operator efficiency.

Fig 3: Graph Metrics

Support for DSE 5.1

DSE OpsCenter 6.1 fully supports DSE 5.1 to provision, manage, and monitor your DSE clusters. In addition, we added support for new features such as SASI indexes and DC Latency metrics.

In addition to all the above goodness that I outlined, we have spent a lot of time focussing on general product stability improvements.

Fig 4: DC Latency Metrics


In summary, DSE OpsCenter delivers critical capabilities for administering and monitoring DataStax Enterprise clusters. DSE OpsCenter 6.1 provides you with a wealth of new features and enhancements that make it easier to provision and monitor DSE clusters.  For more information on DSE OpsCenter 6.1, see our online documentation. To try DSE OpsCenter 6.1 in your own environment, download a copy today and be sure to let us know what you think.

To learn more about the new capabilities in DSE 5.1 release, please check out the following blogs:


DataStax is a registered trademark of DataStax, Inc. and its subsidiaries in the United States and/or other countries.
Apache Cassandra and Cassandra are trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.



Your email address will not be published. Required fields are marked *