OpsCenter Release Notes

OpsCenter release notes provide information about new and improved features, known and resolved issues, and bug fixes.

Release impacts

Understand upgrade impacts, compatibility with DSE versions, and known issues.

Before reading release notes, review the following information to understand upgrade impacts, compatibility with DataStax Enterprise (DSE) versions, and known issues for your version of OpsCenter.

Upgrade Information

Important: Review the upgrade considerations 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 (DSE) are supported with OpsCenter 6.x, see the DSE OpsCenter compatibility with DSE.

Known Issues

Warning: To prevent data loss on OpsCenter 6.7.1 or 6.7.3, do not delete snapshots after a restore. For more information, see the DataStax Support Alerts or contact DataStax Support. (OPSC-15957)
Important: Review the list of known issues before running a new OpsCenter version on a production DSE cluster.

OpsCenter 6.7.4 release notes

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

21 June 2019

Backup Service
  • Agents will now detect if there are symlinks in their DataStax Enterprise (DSE) data directories. If symlinks are detected, OpsCenter displays a warning and On Server snapshot cleanup will not run. (OPSC-15974)
  • Corrected an issue where an On Server bypass restore would place symlinks in working data directories instead of hard links. (OPSC-15957)

OpsCenter 6.7.3 release notes

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

8 May 2019

Highlights

Core

  • Even when configured clusters are unavailable, users can interact with the Cannot connect to cluster screen, including being able to select text or click hyperlinks.

Backup Service

  • If an attempt to create a hard link fails, improved restore error handling allows the restore to fall back to using copy for all future files.
  • The Backup Service now uses the LZ4 algorithm for compression, which makes compressions four times faster, but results in 10% larger files. Older backups that use gzip can still be restored with OpsCenter.

Lifecycle Manager (LCM)

  • Can configure time between polling if DSE is up and running with dse_healthcheck_attempt_wait_time configuration option for LCM.
  • LCM now displays a useful error and link to documentation when trying to edit or use a Config Profile with an unsupported DSE version.

Changes in 6.7.3

The following changes are included in this release.

Core
  • Improved memory handling of tooltips. (OPSC-6524)
  • Fixed an issue where the wrong log4j.properties configuration file was included in the installed_location/agent/conf directory of opscenterd tarball distributions. (OPSC-14729)
  • Fixed an issue where users could not interact with the Cannot connect to cluster screen, including being able to select text or click hyperlinks, when configured clusters are unavailable. (OPSC-15767)
Backup Service
  • Fixed an issue where alert types that permit immediate notification could not be edited if immediate notification was selected. (OPSC-13704)
  • When recreating a keyspace with nested UDTs, fixed dependency order of UDTs to control the order OpsCenter restores the UDTs. (OPSC-15127)
  • Improved restore error handling when an attempt to create a hard link fails. After one such failure, the restore will now fall back to using copy for all future files. (OPSC-15608)
  • Backup service now uses the LZ4 algorithm for compression, which makes compressions four times faster, but results in 10% larger files. Older backups that use gzip can still be restored with OpsCenter. (OPSC-15633)
  • Fixed an issue that prevented some detailed information about backups from displaying in the OpsCenter interface. (OPSC-15200)
  • Added logging to clarify errors the can occur when creating a snapshot with DSE 6.0.3 or DSE 6.0.4. (OPSC-15309)
  • Fixed an issue where the default locations for commit log backups could not be entered in the OpsCenter interface. (OPSC-15683)
  • Fixed a bug where only a subset of keyspaces were shown in the Restore from Backup dialog keyspace selector. (OPSC-15717)
  • Upgraded DSE Java Driver to 1.8.1. (OPSC-15719)
  • Fixed bug in parsing tiered_storage_options. (OPSC-15724)
  • Fixed an issue that would cause a SSTableloader bypass restore to fail if restoring an entire keyspace with materialized views from an On Server location without specifying any tables. (OPSC-15739)
  • Fixed an issue that caused the minimum percentile alerts to return a high value instead of 0 when given only zeros for data. (OPSC-15762)
Monitoring
  • Corrected an issue where an alert could trigger emails even after it was deleted. (OPSC-13861)
Provisioning
  • Definitions added to allow configuration of CASSANDRA_HEAPDUMP_DIR in cassandra-env.sh. (OPSC-12377)
  • LCM will now install appropriate packages to read from the apt-transport-https repository on Debian Stretch. (OPSC-15018)
  • Added more logging to the post-install script for the Debian package installation. (OPSC-15106)
  • LCM now displays a useful error and link to documentation when trying to edit or use a Config Profile with an unsupported DSE version. (OPSC-15381)
  • LCM jobs now always stop the DSE service, even if it thinks the service is already stopped. This can happen if the user is using a different service management system to manually start/stop DSE outside of LCM. (OPSC-15556)
  • Updated LCM to properly call systemctl daemon-reload. (OPSC-15563)
  • LCM install jobs with manual repository setups on systems that use the yum package manager will no longer falsely report that the dse-full package cannot be found. (OPSC-15621)
  • Fixed LCM API uniqueness check for entities on PUT requests when one or more unique key fields are missing from the request. The LCM API now gives an error when the user submits a change for a read-only field. Previously, the LCM API ignored these changes with no error. (OPSC-15656)
  • LCM cluster model and related resources are now immutable while there are associated jobs in the queue. (OPSC-15714)
  • LCM import cluster and DataStax Agent installation jobs will no longer run concurrently with any other job type. This change prevents the troublesome situation where one of these job types is run on a cluster that is already managed while another job type is active on that cluster. (OPSC-15716)
  • Added dse_healthcheck_attempt_wait_time configuration option for LCM to configure the time between polling if DSE is running. (OPSC-15731)
  • Improved tarball extraction in meld to avoid potential too many open files issue. (OPSC-15831)
  • Removed auto download of Oracle JRE due to Oracle licensing changes. (OPSC-15871)
Repair Service
  • Fixed to prevent leaking file descriptors by cleaning up open resources after each repair job completes. (OPSC-15466)
  • Fixed Repair Service alert regression when opscenterd is restarted during repairs. (OPSC-15746)

OpsCenter 6.7.1 release notes

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

cluster_name.conf

The location of the cluster_name.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/clusters/cluster_name.conf
  • Tarball installations: install_location/conf/clusters/cluster_name.conf

opscenterd.conf

The location of the opscenterd.conf file depends on the type of installation:
  • Package installations: /etc/opscenter/opscenterd.conf
  • Tarball installations: install_location/conf/opscenterd.conf

4 March 2019

Highlights

Core

  • Rollover log files for opscenterd and other configured rollover log files are now included in the diagnostic tarball. (OPSC-12141)
  • Made a change to always remove the server response header from opscenterd web server responses for security purposes to combat vulnerabilities in a known version of Twisted web server. (OPSC-14866)
  • OpsCenter now adds the HttpOnly flag to its login session cookie to help prevent XSS attacks. (OPSC-14868)
  • Packages now include extra build information in the following files to aid in troubleshooting and support: ds_branch.txt, ds_version.txt, and ds_timestamp.txt. These files now include branch, commit, version, and timestamp information. (OPSC-15201)

Backup Service

  • Backups to Amazon S3 locations now support Amazon S3 Transfer Acceleration. (OPSC-10271)
  • Added KMS Managed Encryption (SSE-KMS) as an option for Amazon S3 backups. (OPSC-15170)
  • Improved the speed of backups to local file system destinations. (OPSC-15530)
  • Changed restore operations that bypass SSTableloader to use hard links (if possible) instead of copying files to reduce the required disk space when restoring from a destination. (OPSC-14894)
  • Increased the speed when backing up to a local file system and fixed a bug with throttling speed to the local file system. (OPSC-14876)
  • Fixed a bug that could cause problems when restoring materialized views. (OPSC-14727)
  • Fixed an issue where AWS role-based credentials were being held in memory after expiration. (OPSC-15138)

Lifecycle Manager (LCM)

  • Added configuration files in LCM to enable exporting collected metrics from DSE Metrics Collector to supported monitoring tools. (OPSC-15094)
  • LCM now performs client-side health checks against each node in the job by executing a local query before the job is considered successful on that node. (OPSC-14848)
  • Fixed an issue where LCM jobs would fail to terminate when aborted. (OPSC-14410)

Changes in 6.7.1

The following changes are included in this release.

Core
  • Logging levels for OpsCenter and all DataStax Agents in a cluster can now be set with a curl command. (OPSC-7105)
  • The DataStax Agent now supports Transport Layer Security (TLS) with remote JMX. (OPSC-8375)
  • Disconnecting a cluster no longer fails if the cluster configuration file was already removed. (OPSC-11318)
  • The OpsCenter UI now properly escapes all JSON responses returned from its API. (OPSC-11508)
  • Corrected an issue that prevented the failover OpsCenter instance from connecting to the DataStax Agents during failover. (OPSC-11742)
  • Fixed an issue when sending alerts to multiple recipients via email. (OPSC-12131)
  • Rollover log files for opscenterd and other configured rollover log files are now included in the diagnostic tarball. (OPSC-12141)
  • Added multi-role support for LDAP authentication. Added additional roles field to /users and /users/\{username\} GET responses for getting all roles that a user belongs to. (OPSC-12740)
  • Added documentation for the /logout API. (OPSC-13147)
  • Made changes to include the output of DESCRIBE FULL SCHEMA in the diagnostic tarball downloaded from OpsCenter. (OPSC-13290)
  • Fixed an issue with the POST URL event plugin that was logging error messages during successful POST operations. (OPSC-13643)
  • Improved favicon display in several web browsers. (OPSC-13788)
  • Removed non-determinism from RollupReporter restart. (OPSC-13798)
  • DNS names no longer try to resolve during configuration validation. (OPSC-14181)
  • Fixed an issue where OpsCenter indicated that a change to the OpsCenter keyspace replication strategy failed, when selecting the link from the notification about the OpsCenter keyspace using SimpleStrategy for replication in a multi-datacenter environment. (OPSC-14406)
  • OpsCenter now drops compact storage option from all tables inside the configured OpsCenter keyspace. (OPSC-14442)
  • Enhanced OpsCenter to properly log exceptions from LDAP if group names contain Unicode characters. (OPSC-14452)
  • Fixed an issue where tmp_dir settings in the [agents] section of the opscenterd.conf configuration file was not being sent to DataStax Agents. (OPSC-14722)
  • Made a change to always remove the server response header from opscenterd web server responses for security purposes to combat vulnerabilities in a known version of Twisted web server. (OPSC-14866)
  • OpsCenter now adds the HttpOnly flag to its login session cookie to help prevent XSS attacks. (OPSC-14868)
  • Fixed an issue where a benign warning message would be logged when opscenterd started. (OPSC-14912)
  • Reduced memory usage in opscenterd when requests are made to the DataStax Agent. (OPSC-15037)
  • Packages now include extra build information in the following files to aid in troubleshooting and support: ds_branch.txt, ds_version.txt, and ds_timestamp.txt. These files now include branch, commit, version, and timestamp information. (OPSC-15201)
  • Updated DataStax Agent key generation to utilize RSA instead of DSA and updated documentation. (OPSC-15123)
  • Fixed an issue where STOMP would not come up on some platforms using the LANG=C.UTF-8 variable. (OPSC-15251)
  • Upgraded Dojo to version 1.14. This Dojo release addresses security vulnerabilties. See the NIST website for more information. OpsCenter does not use the vulnerable features and previous OpsCenter versions are not affected. (OPSC-15327)
  • Fixed an issue where STOMP is attempting to reconnect, causing OpsCenter to hang. (OPSC-15357)
  • Fixed an issue where OpsCenter generates too many asynchronous CQL queries, which results in a NoHostAvailableException. (OPSC-15461)
  • Fixed an issue where OpsCenter returned an error page instead of redirecting to the login page when authentication was enabled. (OPSC-15630)
Backup Service
  • Added proxy server support for S3 backup and restore. (OPSC-6978)
  • Added support to use system default credentials for Amazon S3 backups. (OPSC-5161)
  • Backups to Amazon S3 locations now support Amazon S3 Transfer Acceleration. (OPSC-10271)
  • Enabled support for restores on DSE clusters using configuration encryption and client-to-node encryption. (OPSC-12312)
  • Improved exception handling relating to periodic failures before and after running the backup script. (OPSC-12405)
  • Fixed an issue that caused backup history pagination to fail when many events shared the same time. (OPSC-12836)
  • Added support for backing up encryption keys other than system_key, plus support for backing up multiple keys. (OPSC-12914)
  • Fixed an issue where a restore would fail if the backup was taken shortly after dropping a column from a table. (OPSC-13029)
  • Removed requirement that the backup_storage_dir must be on the same partition as the DataStax Agent tmp_dir. (OPSC-13108)
  • Fixed an issue where snapshots containing one or more SASI index could not be restored due to an invalid SSTable name exception during the validation checks. (OPSC-13314)
  • Changed commit log archiving when starting the DataStax Agent to handle all commit logs as a batch instead of processing each file individually. (OPSC-13782)
  • Commit logs can now be archived while backing up a snapshot. The execution of the commit log retention policy has been refactored and will now be more consistent. (OPSC-14126)
  • Fixed a small rendering issue in the Restore from Backup: Other Location form. (OPSC-14226)
  • Fixed a bug requiring the user to double click on the plus (+) button when selecting a keyspace from the Create Backup dialog. (OPSC-14228)
  • Upgraded Java AWS SDK to version 1.11.328. (OPSC-14454)
  • Fixed the destination pre-check to fail the entire backup if the pre-check fails. (OPSC-14508)
  • Fixed an issue when using multi-level prefix paths as locations for the Backup Service. (OPSC-14687)
  • Restored marker in the backups location dialogue indicating that AWS key and secret are required for user supplied credentials. (OPSC-14702)
  • Fixed an error that displayed when clicking Cancel after OpsCenter prompts whether you want to delete a scheduled job. (OPSC-14715)
  • Fixed a bug that could cause problems when restoring materialized views. (OPSC-14727)
  • Increased the speed when backing up to a local file system and fixed a bug with throttling speed to the local file system. (OPSC-14876)
  • Fixed an issue where AWS regions specified as remote_backup_region values in the cluster configuration file were not used as bucket defaults. (OPSC-14775)
  • Changed restore operations that bypass SSTableloader to use hard links (if possible) instead of copying files to reduce the required disk space when restoring from a destination. (OPSC-14894)
  • Fixed an issue that caused schema files to be sent repeatedly to a destination during a backup. (OPSC-15009)
  • Reduced memory required when Backup Service is taking a snapshot. (OPSC-15046)
  • Fixed an issue with Point In Time restores when an On Server destination is the only destination defined. (OPSC-15052)
  • Added a fix to sort keyspaces in the selection list. (OPSC-15114)
  • Added node IP in Destination validation error messages. (OPSC-15166)
  • Added KMS Managed Encryption (SSE-KMS) as an option for Amazon S3 backups. (OPSC-15170)
  • Fixed a bug that generated an error indicating that a Solr core could not be created because the associated table did not exist. This error occurred when tables backed by Solr cores were dropped before running the restore, but the keyspace was not dropped. (OPSC-15187)
  • Prevented errors about missing schema.cql for system tables when taking a backup (OPSC-15198)
  • Fixed missing destination UI bug by keeping UI cache of destinations in sync with the server when a backup is run. (OPSC-15206)
  • Fixed a bug where the text value of the button label was passed in the parameter to remove the selected backup destination when selecting Delete Backup Data. (OPSC-15215)
  • Fixed an issue causing restores to fail when restoring a keyspace containing user defined types (UTD). (OPSC-15308)
  • OpsCenter no longer truncates tables in the OpsCenter keyspace even if selected as part of the restore. (OPSC-15310)
  • Changed permissions so that the diagnostic tarball only requires read permissions on files. (OPSC-15382)
  • Fixed a bug with region selection when using the Amazon AWS CLI to use the region specified for the destination. (OPSC-15435)
  • Fixed an issue with the Backup Service and SSTable attached secondary indexes. (OPSC-15489)
  • Improved the speed of backups to local file system destinations. (OPSC-15530)
  • Improved handling of exceptions when trying to back up to an Amazon S3 bucket that does not exist. (OPSC-15544)
  • Fixed a bug where the Location form does not close when adding a new location for a Point In Time restore. (OPSC-15573)
  • Removed dependency of az-cli when using Microsoft Azure for backups. (OPSC-15602)
  • Redacted storage keys from log files when running commands from AzCopy to improve security. (OPSC-15672)
Best Practice Service
  • Fixed an error in the Secondary indexes cardinality Best Practice rule where a list of nodes displayed instead of information about too many secondary indexes in keyspaces and tables. (OPSC-15209)
Monitoring
  • Support added for new Read Coordination and Hint metrics added in DSE 5.0.12 (Read Requests - Local Node Non Replica, Read Requests - Preferred Other Replicas, Hints on Disk, Hint Replay Success Rate, Hint Replay Error Rate, Hint Replay Timeout Rate, Hint Replay Received Rate). (OPSC-12230)
  • Improved the color scheme for node status in OpsCenter. (OPSC-12618)
  • Fixed an issue where the graph zoom button does not work when the legend is expanded. (OPSC-13413)
  • 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.7.x installations. Metric data collected prior to deploying the fix will remain invalid. (OPSC-13657)
  • Fixed an issue where nodes were sometimes incorrectly indicated as DOWN in OpsCenter when they were actually UP. (OPSC-14299)
  • Corrected an unhandled exception when retrieving metrics from clusters with datacenters that contain hyphens in their names. (OPSC-14747)
  • Added current_value_timestamp to data returned by the /alerts/fired route. (OPSC-14762)
  • Implemented a change so that data for average time and average request for Solr cores comes from QueryMetrics MBean rather than older Solr MBeans. (OPSC-14845)
Nodes
  • Fixed an issue where decommissioning a node would sometimes result in an error indicating that OpsCenter “Tried to cancel an already-cancelled event”. (OPSC-14016)
NodeSync
  • Enhanced link styling on the NodeSync status page to make clickable entities more distinct and obvious. (OPSC-15514)
Performance Service
  • Fixed an issue where some configuration parameters in the [agent_config] section of cluster_name.conf could not be parsed by the DataStax Agents. (OPSC-12258)
  • Removed blocking cql queries to improve application performance. (OPSC-15574)
Provisioning
  • Fixed an issue where column names overlapped in the key_provider edit dialog in LCM. (OPSC-10990)
  • Added information about upgrade jobs to the cluster workspace tooltip. (OPSC-13107)
  • Disallow LCM cluster import when opscenterd is not fully communicating with a cluster. (OPSC-13367)
  • Enlarged the ssh-key field in LCM to improve readability when entering SSH keys. (OPSC-13509)
  • Fixed a bug in LCM cluster import when there are datacenter or node-specific configuration options. (OPSC-13546)
  • Fixed a bug where LCM UI form dialogs would reset values to the original state while being edited. (OPSC-14025)
  • Fixed an issue where the native_transport_port_ssl setting was ignored when changing the default CQL password. (OPSC-14030)
  • Added tooltips for several custom URLs to provide examples of what LCM needs them to point to. (OPSC-14060)
  • LCM UI form dialogs now display a loading animation while loading form values on slow connections. Form inputs will be grayed out while in the loading state. (OPSC-14123)
  • Modified the locations that LCM uses to traverse the cluster model when determining the SSH management port. (OPSC-14258)
  • Fixed an issue where LCM jobs would fail to terminate when aborted. (OPSC-14410)
  • Improve LCM error messages when invalid characters are submitted for usernames or entity names. (OPSC-14411)
  • Improved error message when LCM attempts to update the default admin password in the cassandra CQL account, but no new password has been specified on the LCM cluster model. (OPSC-14586)
  • Performing a minor upgrade on yum-based systems when dse-demos is installed no longer upgrades DSE to the latest available version. (OPSC-14608)
  • LCM now performs client-side health checks against each node in the job by executing a local query before the job is considered successful on that node. (OPSC-14848)
  • Added configuration files in LCM to enable exporting collected metrics from DSE Metrics Collector to supported monitoring tools. (OPSC-15094)
  • Fixed a bug preventing node_install_idle_timeout from being respected in LCM. (OPSC-15376)
  • Fixed a bug in LCM platform detection code for Amazon Linux 2. (OPSC-15637)
Repair Service
  • Implemented a fix to prevent the first Repair Service progress alert from being triggered before the period (in seconds) configured by error_logging_window elapses first. (OPSC-13166)
  • When a distributed subrange repair is paused, the current-task file is not removed from the DataStax Agent file system. (OPSC-14612)
  • Parsed the DataStax Agent tokenranges JSON size value as Java long rather than int to avoid crashing due to int overflow during subrange repairs. (OPSC-15182)
  • Prevent Repair Service from crashing due to a Java long overflow when a repair task is persisted in SQLite. (OPSC-15225)
  • Change to use a Java long primitive for calculation to prevent the Repair Service from crashing due to a Java integer overflow. (OPSC-15255)

OpsCenter 6.7.0 release notes

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

5 December 2018

Highlights

  • Upgraded to the new DataStax Enterprise Java driver with full support for DSE 6.7.
  • Added Azure Blob Storage and Amazon S3-compatible storage support for backup and restore operations.
  • When running a restore, OpsCenter now uses a new default restore mechanism that bypasses SSTableloader to significantly increase performance.
  • Meld, the remote execution component of Lifecycle Manager that deploys configuration changes to DSE nodes, no longer depends on a Python runtime.
  • LCM managed Java installations now use OpenJDK instead of Oracle Java.

Review the list of new features in OpsCenter to see the latest additions and compare across versions.

Changes in 6.7.0

The following changes are included in this release.

Core
  • Enhanced OpsCenter to support LDAP searches for users without specifying an Organizational Unit (OU). Also added the ability to follow LDAP referrals. (OPSC-13384)
  • Added a dismissable banner notification concerning Oracle Java policy changes. (OPSC-14672)
  • Upgraded to the new DataStax Enterprise Java driver with full support for DSE 6.7. (OPSC-15060)
Backup Service
  • Added Azure Blob Storage support for backup and restore operations. (OPSC-4777)
  • Added Amazon S3-compatible storage support for backup and restore operations. (OPSC-4994)
  • Removed requirement that the backup_storage_dir must be on the same partition as the DataStax Agent tmp_dir. (OPSC-13108)
  • Changed the restore of materialized views to happen after data is restored. (OPSC-14574)
  • Moved AWS S3 destination validation from OpsCenter to the DataStax Agent. (OPSC-14611)
  • Fixed an issue with where the AWS Credentials Provider Chain was not respected in relations to IAM Roles. (OPSC-14939)
  • Fixed an issue in OpsCenter where editing an S3 destination after a restart shows Enable S3 server-side encryption and Enable S3 transfer acceleration enabled when they are not. (OPSC-14982)
  • Corrected an issue that caused the restore status to initially show 100% then reset to 0%. (OPSC-14995)
  • Added a loading indicator to the Configure and Restore screen when populating the list of keyspaces and graphs. (OPSC-14999)
  • Fixed a memory leak in the Backup Service job execution cache. (OPSC-15015)
  • When running a restore, users now have the ability to bypass SSTableloader. (OPSC-15038)
  • Fixed an issue with point-in-time restores when an On Server destination is the only destination defined. (OPSC-15052)
  • Fixed Solr restore handling to be case sensitive. (OPSC-15117)
  • Fixed a bug that generated an error indicating that a Solr core could not be created because the associated table did not exist. This error occurred when tables backed by Solr cores were dropped before running the restore, but the keyspace was not dropped. (OPSC-15187)
  • Updated restore logic so materialized views will be restored if their underlying table is recreated. (OPSC-15188)
  • Added a note and a warning that when restoring a DSE Graph backup without selecting Use sstableloader, DSE must be restarted to ensure all data is available. (OPSC-15283)
Provisioning
  • Improved LCM error messages for Oracle JRE download errors. (OPSC-13846)
  • Meld, the remote execution component of Lifecycle Manager that deploys configuration changes to DSE nodes, no longer depends on a Python runtime. (OPSC-14076)
  • Changed Opscenterd to OpsCenter in various error-messages and strings. If API clients or log parsers key behavior off of that string, they must be updated. (OPSC-14191)
  • Updated third-party dependencies for LCM. (OPSC-14495)
  • Improved error messages when LCM fails to upload Meld to the target nodes. (OPSC-14517)
  • LCM managed Java installations now use OpenJDK instead of Oracle Java. Existing installs will be migrated to OpenJDK during the next install/upgrade job if no action is taken. See the Upgrade Guide for details. (OPSC-14674)
  • Updated the Java setup page to only display JCE options when manage-java is selected. (OPSC-14897)
  • Improved LCM error message when the Oracle JRE download times out on a target node. (OPSC-14844)
  • The DSE health check timeout (dse_healthcheck_startup_timeout) can now be set to configure how long LCM will wait for DSE to start up. (OPSC-15014)
  • Field descriptions now display by default in LCM configuration profiles. (OPSC-15036)
  • LCM health checks for DSE startup now retry if the service script says the service is not running. It was observed that the status might be inaccurate early on during service start. (OPSC-15043)
  • LCM now defaults to setting auto_bootstrap to true for all nodes. This change improves install-job robustness, but requires that initial node startup be performed one at a time. Concurrency policies other than Automatic (default) are not recommended. (OPSC-15189)
  • The default job concurrency policy in LCM now behaves the same as the Single install policy. This default improves robustness of install jobs at the cost of executing jobs more slowly. (OPSC-15192)
  • The meld.pyz file name changed to meld. (OPSC-15817)
Repair Service
  • Fixed a bug for Distributed Subrange Repair (DSR) to honor the max_parallel_repairs property, which was remaining at a value of 1 regardless of the specified value. (OPSC-14947)

Known and resolved issues for OpsCenter 6.1 and later

Known issues, workarounds, and resolved issues for the OpsCenter and Lifecycle Manager 6.1 and later versions.

The following are known issues that exist in OpsCenter 6.1 and later versions. Each item has a link to more details including workarounds when available. These issues will be addressed in future releases where possible. If you have any questions, contact DataStax Support for assistance.

OpsCenter 6.7.1 and 6.7.3
  • Data loss can occur if you delete the contents of the snapshot directory after using OpsCenter to perform a restore operation from an on-server backup to a cluster with an unchanged topology. (OPSC-15957)
    Warning: To prevent data loss on OpsCenter 6.7.1 or 6.7.3, do not delete snapshots after a restore. For more information, see the DataStax Support Alerts or contact DataStax Support.
OpsCenter 6.5.0
  • When running an LCM job and attempting to abort or terminate the job while it is in progress, termination fails to stop the job unless the abort request is issued prior to the first node completing. Issuing a terminate or abort command after the first node has finished running has no effect. The job will continue to run to completion as if the terminate command had not been issued. (OPSC-14410)
OpsCenter 6.1.x and 6.5.0
  • OpsCenter does not automatically remove compact storage from its keyspaces when upgrading to OpsCenter 6.5.0. For important details, see Compact storage no longer supported. (OPSC-14442)
OpsCenter 6.1 and later
  • For DSE versions 5.1 and later, slow query data is only available since the last time the DataStax agent was restarted. (OPSC-11702)
  • 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)
  • When using OpsCenter to restore a backup that contains multiple SASI indexes, some or all of these indexes might not restore correctly. The indexes appear in the table schema but might not function correctly. Indexes should be validated at restore time and rebuilt if errors are detected. For more information, see CREATE CUSTOM INDEX (SASI). (OPSC-11746)
    Note: SASI indexes are experimental for DSE. DataStax does not support SASI indexes for production.
OpsCenter 6.1
  • A large number of log messages might display regarding requests to /pit-cleanup if there are a large number of existing commit logs in the staging directory. (OPSC-8349)
  • 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)
  • Enabling SNMP alerts may cause opscenterd to hang on startup in some slower environments. (OPSC-9314; see More Details)
  • For DSE versions earlier than 5.0.7, the DataStax Agent can only estimate partition sizes and counts per node or keyspace for repairs by using JMX stats. For DSE versions 5.0.7 and later, the Datastax Agent queries the system size_estimates table for a more precise estimate of partition sizes and counts per range. (OPSC-11417, OPSC-11590)
  • For DSE versions 5.0 and later, object permissions currently are not persisted with an OpsCenter backup and thus are not re-applied when that backup is restored. As a result, users must manually manage object permissions externally from OpsCenter. For more details (no workaround available at this time), see the KB support article. (OPSC-11015)
  • The solr-index-size (displayed as Search: Core Size) metric in the OpsCenter Monitoring UI is unavailable for DSE versions 5.1.0 through 5.1.3. (OPSC-12267)
  • Lifecycle Manager (LCM)

    • 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)