OpsCenter 6.5.1 Release Notes

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

Highlights

  • OpsCenter now drops compact storage option from all tables inside the configured OpsCenter keyspace.
  • Fixed an issue where LCM jobs would fail to terminate when aborted.
  • Fixed a bug in the repair service parallel repairs calculation for subrange repairs.

See New features for more details.

Upgrade Information

Important: Review the 6.5.1 changes pertinent to the release as noted in Upgrading DSE OpsCenter. 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

  • Removed arrow from Refresh label in Event log. (OPSC-14316)
  • OpsCenter now drops compact storage option from all tables inside the configured OpsCenter keyspace. (OPSC-14442)
  • Fixed an issue where the DataStax agents would always verify subject alternative names in certificates if the STOMP address was a hostname. (OPSC-14551)

Backup Service

  • Added support to use system default credentials for Amazon S3 backups as described in https://docs.aws.amazon.com/sdk-for-java/v2/developer-guide/credentials.html. (OPSC-5161)
  • Enabled support for restores on clusters with Kerberos. (OPSC-14236)
  • Fixed an issue where a restore would fail if the backup was taken shortly after dropping a column from a table. (OPSC-13029)
  • Added support to configure the backup storage directory (backup_storage_dir) using the commit log backup settings. (OPSC-14496)
  • Optimized backup file comparison synchronization. (OPSC-14559)

Performance Service

  • Fixed Read Stage and Mutation Stage best practice rules when running on DSE 6.0 (OPSC-14430)

Repair Service

  • Fixed a bug in the repair service parallel repairs calculation for subrange repairs. Previously, while calculating the required number of parallel repairs, the current number of parallel repairs allowed was not taken into account. This would lead to the repair service running significantly less repairs in parallel than the configured maximum allowed even when repair throughput was lower than needed to complete the full repair cycle by the completion deadline. The updated algorithm resolved the issue. (OPSC-13172)
  • Eliminated unnecessary logging when the repair service is running tasks at the max rate. (OPSC-14476)
  • Fixed a bug that prevented a repair cycle if the Repair Service was unable to find a task to run of over max_down_node attempts. (OPSC-14733)

Provisioning

  • Fixed an issue where LCM jobs would fail to terminate when aborted. (OPSC-14410)

Dashboard

  • Fixed an issue where cluster overview sparklines would load, but not update. (OPSC-13913)