OpsCenter 5.2.3 Release Notes
Release notes for the OpsCenter version 5.2.3 release.
Backup Service
- Schema issues detected during the restore pre-check will now be presented in a dialog and the user can choose to force the restore despite the issues. (OPSC-6257)
- The timeout for validating AWS S3 buckets when saving backups through the UI has been increased to a default of 30 seconds. The timeout can be increased as a temporary workaround via the [ui].default_api_timeout parameter in opscenterd.conf. (OPSC-6077)
- Fixed an issue with restoring tables containing User Defined Types that were backed up in OpsCenter 5.1.x and restored in OpsCenter 5.2.x. (OPSC-7000)
- Fixed an issue that prevented commitlogs from being properly cleaned up when a retention policy was defined in commitlog archiving. (OPSC-5439)
- Fixed an issue that prevented validation of PIT restores from failing as expected if the DSE/DSC version information is unavailable. (OPSC-6686)
- Fixed an issue where the AWS S3 throttle value entered in the UI was not used when copying a backup to AWS S3. Also removed the AWS S3 throttle option from the restore snapshot dialog in the UI because it is not yet supported. (OPSC-6967)
- Fixed an issue with the removal of temporary destinations from the cluster configuration file when an ad-hoc backup to that destination was deleted. (OPSC-6583)
- Fixed an issue where table details for a restore would not be displayed when started using the api and the specific tables for the keyspace were not specified. (OPSC-4242)
- Fixed an issue where the backup settings tab was referred to by another name in the point in time restore dialog. (OPSC-6770)
- Exposed new configuration options to increase the history of job statuses stored on the agent. More information about the symptoms and solution can be found here: https://support.datastax.com/hc/en-us/articles/206456076. (OPSC-6916)
Diagnostic Tarball
- GC logs have been added to the diagnostics tarball. (OPSC-1522)
- The diagnostic tarball includes the address.yaml agent config file. (OPSC-7156)
- Fixed an issue with the diagnostic tarball not collecting `cqlsh` output for clusters running DSE 4.7 or later. (OPSC-7035)
Improvements
- Dropped messages metrics are now more useful by displaying changes over time rather than a running total. (OPSC-6393)
- Best Practice Service rules no longer fail due to agents being disconnected or unavailable. A special indicator will now appear next to the status of rules that did not fail but had issues connecting to one or more agents. (OPSC-3705)
- Improved error handling when collecting Solr metrics that caused no metrics to be collected when one metric had an issue. (OPSC-7123)
Resolved Issues
- Fixed an issue where LDAP users whose CNs contained special characters were unable to sign in. (OPSC-6914)
- Fixed an issue that prevented OpsCenter from running behind a proxy. Previously, the system used by the UI to poll opscenterd for updates had an absolute URL that made using a proxy difficult. (OPSC-2541)
- Opscenterd will no longer log the value of [cassandra].password and [agents].ssl_keystore_password when using a separate storage cluster. (OPSC-7024)
- When using config file encryption with a separate storage cluster, the ssl_keystore_password and password options for both storage and monitored clusters can now be encrypted. (OPSC-7025)
- Fixed an issue that caused corrupt Dashboard data to prevent all Dashboards from loading. (OPSC-6991)
- Fixed an issue where the rebalance algorithm would fail on some rack-aware clusters. (OPSC-3194)
- Resolved some memory leaks from the UI. (OPSC-6027)
- Fixed an issue where the hadoop job values for the status and duration did not update as the job was running. (OPSC-5317)
- Fixed a bug in the Repair Service in which OpsCenter was giving Cassandra too large of a range to repair within a reasonable time window. (OPSC-5955)
- Clicking the Services icon on the left navigation pane now refreshes the status of the services displayed on its landing page. (OPSC-6400)
Compatibility
To see which versions of OpsCenter are compatible with the various Cassandra and DataStax Enterprise versions, see the OpsCenter Compatibility chart.