OpsCenter Release Notes

Added support for DataStax Graph (DSG).

Added the ability to enable incremental NodeSync.

Upgraded to the new DataStax Enterprise Java driver with full support for DSE 6.8.

Updated DataStax Agent to be compatible with Java 11.

Fixed an issue that caused a 404 error when retrieving an xref:configure/agentAddressConfiguration.adoc value of false from the DSE Agent.

Fixed vulnerabilities in the OpsCenter user interface. (OPSC-16221)

Updated c3p0 library to prevent vulnerabilities in OpsCenter. (OPSC-16109)

Updated dependency of JGroup to prevent vulnerabilities in OpsCenter. (OPSC-16105)

Updated DataStax Agent to be compatible with Java 11. (OPSC-15278)

Fixed a logging issue related to querying the status of the Performance Service while DataStax Agents are not connected. (OPSC-13014)

Removed phone home feature from OpsCenter. (OPSC-8756)

Added an authentication plugin framework to allow custom authentication strategies. (OPSC-14507)

Changed default user interface timeout from 10 seconds to 30 seconds. (OPSC-15554)

Added hostname verification for LDAP SSL/TLS connections by default. (OPSC-16354)

Fixed an issue where OpsCenter metrics storage would limit queries incorrectly to a subset of nodes. (OPSC-12413)

Fixed an issue that caused a restore to fail when working with tens of thousands of SSTables for a single node and keyspace. (OPSC-16463)

Fixed an issue causing unneeded checks of remote file sizes during restore. (OPSC-16431)

Fixed an Azure backup issue where not all data was being returned when a container had more than 5000 items. (OPSC-16409)

When running a backup for select datacenters, the disk space check no longer queries nodes not included in the backup. (OPSC-16407)

Fixed issues preventing a sstableloader bypass restore of a single datacenter. This works with only new backups of the datacenter. (OPSC-16341)

Corrected an issue that prevented a datacenter snapshot from being taken when nodes outside of that datacenter had problems with their DataStax Agents. (OPSC-16338)

Corrected a performance problem with the keyspace selector for clusters with a large number of keyspaces or tables. (OPSC-16331)

Added support for Swift S3 backup and restore. (OPSC-16240)

Improved error message when a node does not have access to the data required for a restore. (OPSC-16042)

Fixed an issue which could cause a StackOverflowException during backups, restores, and metrics gathering. (OPSC-15977)

Optimized how commit logs are transferred to destinations when the DataStax Agent starts. (OPSC-14023)

Added support for DataStax Graph (DSG) backups. (OPSC-14699)

Reduced instances of thread death. (OPSC-10385)

Added commit log archiving failures as alerts in the OpsCenter event log. (OPSC-14020)

Added support to configure the backup storage directory (backup_storage_dir) using the commit log backup settings. (OPSC-14496)

Fixed an issue when using multi-level prefix paths as locations for the Backup Service. (OPSC-14687)

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 for new DataStax Graph (DSG) metrics. (OPSC-15876)

Removed the following metrics to reflect definitions for DataStax Enterprise 6.8.0. (OPSC-15588)

Added support to enable and disable incremental NodeSync introduced in DataStax Enterprise 6.8.0. (OPSC-15798)

Added new NodeSync Incremental Validation Covered Ages metric for incremental NodeSync. (OPSC-15654)

Added the ability to specify CASSANDRA_LOG_DIR via Lifecycle Manager by managing dse-env.sh. (OPSC-16307)

Fixed an issue in Lifecycle Manager that caused the movement of temporary files across file systems to fail when /tmp is mounted on its own file system. (OPSC-15822)

Added ability to configure DSE defaults for environment variables. (OPSC-15211)

When editing SSH keys in Lifecycle Manager within the SSH credential form, the keys are now displayed in a monospace font. (OPSC-15087)

OpsCenter and DataStax Enterprise no longer require the external binary which to be installed. (OPSC-14931)

Lifecycle Manager does not allow for the following cluster names: opscenter, api, login, logout, rc, and keepalive. (OPSC-14119)

Updated logging to include additional logging from some dependencies. (OPSC-13180)

Made UTC the default logging time zone for OpsCenter and DataStax Agents. Added time zone specifier to log timestamps. (OPSC-15405)

Repair Service temporary files are cleaned up more quickly. (OPSC-15982)

Data might not display on graph queries for graphs restored with OpsCenter. This occurs under the following conditions:

When restoring materialized views, OpsCenter does not correctly wait for the cluster schema to settle, which can cause errors when data is restored to the table on which the view is based. (OPSC-13029)

If there are approximately 75 or more keyspaces, the DataStax Agent /tokenranges API call runs out of memory with the default heap size. As a temporary workaround, adjust the agent heap size. (OPSC-11975)

For DSE versions 5.1 and later, slow query data is only available since the last time the DataStax agent was restarted. (OPSC-11702)

Insufficient permissions on the staging directory can cause the agent to exhaust inotify watches on the system over time. (OPSC-10732)

Users will see an ungraceful error+stack trace in opscenterd.log if accessing a cluster through the UI/API that no longer exists. The error message contains “ERROR: Unhandled error in Deferred: There are no clusters with name or ID…​”. This error message is harmless. (OPSC-8819)

Lifecycle Manager is not currently compatible with DSE Transparent data encryption. See Encrypted DSE configuration values for more details. (OPSC-7529)

DSE Graph properties: DSE Graph configuration in dse.yaml, which is configurable through LCM Config Profiles. All Graph properties in dse.yaml can be managed through the LCM UI with the exception of gremlin_server.serializers and gremlin_server.scriptEngines. If you are using LCM and need to customize these properties, be sure to leverage the LCM API to make the changes. Future changes to the Config Profile using the LCM UI will retain properties set through the API.

When configuring credentials in a Repository, special characters such as #, $, and so forth are supported, but non-ascii unicode characters are not. (OPSC-8921)