OpsCenter 6.1.7 Release Notes

Release notes for the OpsCenter version 6.1.7 release.

Highlights

Implemented DSR (Distributed Subrange Repair) as an alternative implementation of subrange repairs within the OpsCenter Repair Service, intended to better scale for large clusters. See Enabling distributed subrange repairs.

Upgrade Information

Important: Please be sure to review the 6.1 changes pertinent to the release as noted in the DataStax OpsCenter Upgrade Guide. Configuration and other notable changes are provided in detail.

Compatibility

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.

Core

  • Sensitive password fields in the cluster configuration are no longer returned by the API. (OPSC-4361)
  • Added a dialog to OpsCenter UI prompting the user to refresh the browser when the underlying OpsCenter server version has changed. (OPSC-11254)
  • Fixed an issue where nodes would be incorrectly marked as DOWN when they are in fact UP after being added again to the cluster. (OPSC-13408)
  • Fixed an issue where opscenterd would not always properly update a node's UP/DOWN state based on the number of peers that report the node to be down. (OPSC-13909)
  • Fixed a bug where dialogs in OpsCenter would reposition incorrectly when the dialog contents changed size. (OPSC-13914)

Monitoring

  • Fixed an issue causing invalid data for the Total Compactions Completed metric. The fix will be published as a live definition file update for all existing OpsCenter 6.1.x installations. Metric data collected prior to deploying the fix will remain invalid. (OPSC-13657)
  • Fixed an issue with the node name and IP background color in the Ring view. (OPSC-10635)

Backup Service

  • Removed an outdated 3rd-party URL used in an SSTableloader max heap size error message. (OPSC-13794)
  • Fixed an issue that could cause backup SSTable cleanup on a destination to miss some files. (OPSC-13223)
  • Fixed an issue with backup S3 and local destination file sync that would abnormally halt when errors occurred during the sync. (OPSC-13957)
  • Fixed a bug that in some cases prevented restore of backups taken from prior versions of OpsCenter. (OPSC-14034)
  • Fixed a bug that prevented restore of a point-in-time (PIT) backup if the On Server destination was missing the snapshot files. (OPSC-14370)
  • Fixed a bug that caused errors in the agent log when syncing commit logs to destinations. (OPSC-13645)
  • Corrected an issue with truststore argument to SSTableloader during restore. (OPSC-13686)
  • Optimized backup file comparison synchronization. (OPSC-14559)

Best Practice Service

  • Fixed an issue where the Best Practice Service would flag multiple networks in the network check when there is only one network that is not a loopback device. (OPSC-13190)

Performance Service

  • Fixed a bug in the Table view of Performance Service where the Node grid would not render. (OPSC-13959)

Repair Service

  • Implemented the DSR (Distributed Subrange Repair) feature, which is an alternative implementation of subrange repairs for the OpsCenter Repair Service. DSR is designed to scale for larger clusters by distributing more work to the agents. (OPSC-13531)
  • Added the use_distributed_subrange_repair config option to the Repair Service for running distributed subrange repairs (DSR). (OPSC-13538)
  • The Repair Service no longer creates or uses a clustername.json persistence file. (OPSC-13306)
  • Replaced in-memory repair tasks management with a SQLite database to avoid OOM errors when generating a large number of subrange tasks. (OPSC-13543)
  • Switched to streaming json parsing/generation of large HTTP responses when gathering token ranges from agents as well as generating keyspace metadata for the UI to avoid generating large data structures in-memory. (OPSC-13543)
  • Fixed a bug where repair service would resume prematurely if a cluster topology change was longer than the configured resume timeout. (OPSC-12165)

Lifecycle Manager (LCM) Provisioning

  • Improved the usability of the Rack field in the LCM Add/Edit Node dialog by adding an autocomplete combo box to retain previously entered rack names for selection. (OPSC-13205)
  • Tabbing behavior in the LCM UI has been improved. (OPSC-13204)
  • Fixed a bug in LCM cluster import when there are datacenter- or node-specific config options. (OPSC-13546)