OpsCenter 6.5.0 Release Notes

Release notes for the OpsCenter and Lifecycle Manager version 6.5.0 release.

17 April 2018


  • Support for DSE 6.0
  • NodeSync Service
  • Lifecycle Manager improvements: support upgrading DSE versions on a datacenter or node within a supported release series; cloning and error validation in config profiles.

See New features for more details.

Upgrade Information

Important: Review the 6.5 changes pertinent to the release as noted in Upgrading DSE OpsCenter. Configuration and other notable changes are provided in detail.


To see which versions of DataStax Enterprise are supported with OpsCenter 6.x, see the OpsCenter Compatibility chart.

Known Issues

Important: Please be sure to review the list of known issues before running a new OpsCenter version on a production DSE cluster.

Changes in this release

The following changes are included in this release.

  • Updated to the 1.6.2 version of the DSE driver. (OPSC-12624)
  • The agent can now be configured to enforce that certificate subjects match the opscenterd server. (OPSC-11806)
  • Opscenterd now only allows the TLSv1.2 protocol when HTTPS is enabled. (OPSC-11981)
  • Removed support for DSE versions older than 5.0. (OPSC-12784)
  • Improved default algorithm (rsa 2048) and hash (SHA256) for automatically generated self-signed TLS certificates. (OPSC-9941)
  • OpsCenter will fail to start if config_encryption_active is True and the system key file is missing. (OPSC-10284)
  • The first cluster that a role has permissions for is now automatically selected in the Cluster list of the Edit Role dialog. (OPSC-11759)
  • The default max heap size of the DataStax Agents has been increased to 1GB so that it better supports metrics collections in mid-large size clusters. The default heap size of opscenterd has also been increased to 2GB to better support the Repair Service. (OPSC-12313)
  • OpsCenter uses the G1 garbage collector instead of the Concurrent Mark-Sweep (CMS) garbage collector. (OPSC-12548)
  • OpsCenter and the DataStax Agent have added support for the new native_transport_* parameters introduced inside of cassandra.yaml in DSE 6.0. (OPSC-13181)
  • Tables in the OpsCenter schema are no longer created with compact storage because this feature has been removed in DSE 6.0. For more information, see the DSE upgrade guide (5.1 to 6.0) and the CQL commands for migrating from compact storage (DSE 5.1.x), or the DSE upgrade guide (5.0 to 6.0) and the CQL commands for migrating from compact storage (DSE 5.0.x) to CQL table format, depending on the DSE version. (OPSC-13527)
  • Fixed handling of API errors when enabling or disabling Alert Rules. (OPSC-12814)
  • Fixed timeout that caused the OpsCenter UI to fail to load. (OPSC-13053)
  • For DSE version 6.0 and later, the DataStax Agent no longer collects information about nodetool thriftstats in diagnostic tarball generation because it has been removed from DSE. (OPSC-13560)
  • Updated opscenterd to use CQL rather than HTTP to create Solr cores when necessary. (OPSC-12621)
  • The primary OpsCenter instance URL for failover can now be configured in the opscenterd.conf file. (OPSC-5409)
  • The cluster configuration and the DataStax Agents now have a configurable timeout for read timeout requests for both monitored and storage clusters through the DataStax Java driver. (OPSC-13919)
  • The agent now sends its agent_rpc_broadcast_address to opscenterd at the longtime_interval configured in address.yaml. This improves the agent's ability to auto connect to opscenterd when using dense nodes. (OPSC-14049)
  • Fixed an issue with scrolling to a highlighted activity during bulk operations in the Activities area of OpsCenter Monitoring. (OPSC-5651)
  • Added support for NodeSync metrics. (OPSC-10611)
  • New dropped message metrics have been added, whereas the TP: Dropped Paged Range Reads and TP: Dropped Request Responses metrics have been removed for DSE 6.0 and later. Several metrics regarding dropped messages have had their labels changed from TP: <message type> to Dropped Messages: <message type>. See Dropped Messages metrics. (OPSC-12777)
  • Additional thread pool metrics have been added for monitoring DSE 6.0 and later. (OPSC-12839)
  • Pagination in Activity Event Log now works correctly upon navigating back to first events page. New events can be fetched from server by clicking on Refresh from first page. (OPSC-4937)
  • Fixed an issue with Dashboard graph line colors when switching from a percentile graph in OpsCenter Monitoring. (OPSC-5258)
  • Updated metric descriptions to warn that key cache metrics only apply to pre-DSE 6.0 SSTables. (OPSC-13368)
Backup Service
  • OpsCenter restore will now recreate a graph if a graph was present at backup. (OPSC-11505)
  • Fixed an issue with restore that prevented additional indexes from being recreated when the restored table also included a Solr core. (OPSC-12756)
  • Graphs are now represented as top level objects in the restore workflow. Keyspaces that are part of a graph are now bundled together and are no longer shown individually when restoring a graph backup. (OPSC-12989)
  • Added an endpoint to the API that fetches a dictionary to the graphs and their associated keyspaces that are present in a particular snapshot. (OPSC-13007)
  • The AWS CLI feature for bulk uploading backups to Amazon S3 has been promoted from an OpsCenter Labs feature to an official production feature. Adjust your use_s3_cli configuration settings from the [labs] section to the [backups] section. (OPSC-13165)
  • Changed how the On Server commit log storage works. Commit logs are still initially moved into the backup_staging_dir, but after the commit logs have been sent to any other configured locations, the commit logs are moved to the directory specified by a backup_storage_dir defined in address.yaml. This approach should resolve a number of problems customers have encountered when restarting agents due to large numbers of On Server commit logs being reprocessed. See Configuring commit log backups for details. (OPSC-14073)
NodeSync Service
  • Added support for DSE NodeSync. (OPSC-12602)
  • NodeSync status has been added to the Nodes Services panels in OpsCenter Monitoring. (OPSC-13301)
  • Added a NodeSync Service section to enable NodeSync and view NodeSync status for a cluster's keyspaces and tables. (OPSC-13281)
  • Added a Best Practice rule to validate that the NodeSync Service is running on every cluster node. (OPSC-13064)
Repair Service
  • The parallel_tasks_update_interval configuration option has been added to the Repair Service. (OPSC-14252)
Best Practice Service
  • Added a Best Practice rule to validate that the NodeSync Service is running on every cluster node. (OPSC-13064)
Lifecycle Manager (LCM) Provisioning
  • Added the ability to clone Config Profiles in Lifecycle Manager. (OPSC-6428), (OPSC-12595)
  • Repository setup in Lifecycle Manager is now optional for those who manually configure and manage their package repos externally from LCM. (OPSC-12343)
  • LCM will now drain nodes (stops accepting writes and flushes memtables) before they are restarted. This provides additional safety and speeds up restarts. (OPSC-12581)
  • LCM UI edit config profile page can now display multiple field validation errors, and makes it easy to navigate between errors. (OPSC-12615)
  • LCM has the ability to upgrade DSE on existing (previously installed) datacenters and nodes when assigning a new config profile with a higher DSE version patch. Upgrade the DSE version in LCM within a minor patch release series in DSE versions 5.0.x, 5.1.x, and later. (OPSC-9570), (OPSC-12721)
  • LCM is now using React 15.6.2, up from React 0.14.8. (OPSC-12808)
  • Added concurrency options when executing a job on a cluster. (OPSC-5120)
  • When authentication is enabled, it is no longer necessary to enter credentials in the Job dialogs every time a job is run. After enabling authentication in a Config Profile, entering credentials at the cluster level is required only one time. Future credential changes are allowed. (OPSC-9439)
  • Added job events to job detail screen and made job detail node list more informative. (OPSC-9572)
  • Improved the ability of LCM to recover from some Java installation errors. (OPSC-10400)
  • LCM now includes all explicit node IP addresses when attempting to connect to the cluster for changing the default cassandra user password. This should fix password change for certain network setups. (OPSC-11096)
  • Job termination in LCM will now wait for PID file removal for about 10 seconds before giving up. This should reduce the frequency of the abort ending before Meld has had a chance to shutdown cleanly. (OPSC-11099)
  • LCM API requests can now return multiple errors. (OPSC-11131)
  • A Show/Hide field descriptions button has been added to LCM for those fields that have descriptions or tooltips available. (OPSC-12283)
  • LCM job event detail may now contain a 'source' field containing the property path of the data related to the event. (OPSC-12340)
  • Configuration data in LCM is now validated against the definition files. This ensures proper structure and value types for config profile data. (OPSC-12433)
  • Configuration profile data is now validated against field dependencies in the definitions. This prevents inconsistent configuration data. (OPSC-12434)
  • LCM error responses now consistently use the message key for error text. (OPSC-12438)
  • The LCM API base URL has changed from v1 to v2. For additional details regarding LCM API updates, see LCM API version updates in the OpsCenter Upgrade guide. (OPSC-12500)
  • All passwords in Lifecycle Manager now require double entry for confirmation. (OPSC-12563)
  • Added OpsCenter and Lifecycle Manager support for DSE version 6.0.0. (OPSC-12634)
  • Updated serial install logic in converged DCs to be specific to the Automatic concurrency level. (OPSC-12780)
  • Added definition to support DSE startup property -Dcassandra.force_3_0_protocol_version=true. (OPSC-12944)
  • Added ability to filter on null values to LCM API. (OPSC-12990)
  • Updated dependency versions. (OPSC-13141)
  • Updated Korma version to latest. (OPSC-13170)
  • Lifecycle Manager edit dialogs for SSH credentials, repositories, and clusters now clearly indicate whether passwords have been set and provide change options. Removing a stored password is now an explicit option; inadvertently removing a stored password is no longer possible. (OPSC-13239)
  • Rearranged the Edit Credential comment field to be displayed after required fields on LCM UI. (OPSC-13621)
  • Improved the UI in LCM config profiles by providing additional room for custom list items. (OPSC-13680)
  • The workload options in the LCM Add Datacenter dialog have been renamed to align with DataStax products: Solr is now DSE Search; Spark is now DSE Analytics. (OPSC-13758)
  • Updated the LCM UI and API to reflect the DSE 6.0 rename of rpc_address and broadcast_rpc_address to native_transport_address and native_transport_broadcast_address respectively. (OPSC-13843)
  • Fixed a bug in LCM node IP address inheritance for broadcast_rpc_address. It now defaults to thenative_transport_address (formerly rpc_address) setting, as indicated by the UI form. (OPSC-11970)
  • LCM will no longer inherit profile properties from a parent level when there are config profiles in a cluster topology for different DSE versions. Instead, the profile at the lowest topology level takes precedence and a warning is posted in the job events. (OPSC-12314)
  • Fixed a bug in LCM cluster import when there are datacenter- or node-specific config options. (OPSC-13546)
  • Fixed an issue with configuring Graph serializers in dse.yaml. (OPSC-13955)
  • Added warning about using a remote JMX connection without authentication. (OPSC-13982)
  • Fixed a bug where LCM UI form dialogs would reset values to original state while editing. (OPSC-14025)