OpsCenter Release Notes

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

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 the OpsCenter version.

Upgrade Information

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

Known Issues

Important: Review the list of known issues before running a new OpsCenter version on a production DSE cluster.

OpsCenter 6.5.4 release notes

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

4 December 2018

Highlights

  • Implemented a fix for a critical bug that caused all active, compressed SSTable backups to be cleaned up unnecessarily, resulting in incomplete backups. Active, uncompressed SSTable backup files were unaffected.
  • Enabled support for restores on DSE clusters using configuration encryption and client-to-node encryption.

Changes in 6.5.4

The following changes are included in this release.

Core
  • Made changes to include the output of DESCRIBE FULL SCHEMA in the diagnostic tarball downloaded from OpsCenter. (OPSC-13290)
  • Enhanced OpsCenter to support LDAP searches for users without specifying an Organizational Unit (OU). Also added the ability the to follow LDAP referrals. (OPSC-13384)
  • 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 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)
  • Upgraded Dojo to version 1.14, which includes security patches. See the NIST website for more information. (OPSC-15327)
Monitoring
  • 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)
Backup Service
  • 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)
  • Removed requirement that the backup_storage_dir must be on the same partition as the DataStax Agent tmp_dir. (OPSC-13108)
  • Fixed a small rendering issue in the Restore from Backup: Other Location form. (OPSC-14226)
  • 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)
  • 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)
  • 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)
  • Prevented errors about missing schema.cql for system tables when taking a backup (OPSC-15198)
  • 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)
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)
Provisioning
  • Improved error message returned when the $JAVA_HOME environment variable is invalid. (OPSC-14390)
  • 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)
  • 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)
  • 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)
  • Added the ability to have LCM transfer meld to a node using SCP rather than SFTP. The default behavior is to try SFTP first and fall back to SCP if a failure occurs. This option can be configured using the meld_upload_method parameter. (OPSC-15221)
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)
  • Added safeguards to prevent orphaned repair tasks from affecting the currently running repair jobs, which could have caused Repair Service jobs to deadlock. (OPSC-14218)
  • 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)
  • Implemented a change to use Java long to prevent the Repair Service from crashing due to Java int overflow during subrange repairs. (OPSC-15182, OPSC-15255)

OpsCenter 6.5.3 release notes

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

10 September 2018

Highlights

Implemented a fix for a critical bug that caused all active, compressed SSTable backups to be cleaned up unnecessarily, resulting in incomplete backups. Active, uncompressed SSTable backup files were unaffected.

See New features for more details.

Changes in 6.5.3

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)
  • 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)
  • Corrected an issue that prevented the failover OpsCenter instance from connecting to the DataStax agents during failover. (OPSC-11742)
  • Improved favicon display in several browsers. (OPSC-13788)
  • Reduced memory usage in opscenterd when requests are made to agents. (OPSC-15037)
Backup Service
  • Fixed an issue when using multi-level prefix paths in 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 issue where remote_backup_region values specified in the cluster configuration file were not used as bucket defaults. (OPSC-14775)
  • Fixed an issue with AWS Credentials Provider Chain related to IAM Roles. (OPSC-14939)
  • Fixed an issue in the UI where editing an Amazon S3 destination after restarting OpsCenter shows Enable S3 server-side encryption and Enable S3 transfer acceleration enabled when they are not. (OPSC-14982)
  • Fixed an issue that caused schema files to be repeatedly sent to a destination during a backup. (OPSC-15009)
  • Fixed a memory leak in the backup job execution cache. (OPSC-15015)
Repair Service
  • Omit verbose C3P0 logging from agent log file. (OPSC-14176)
  • Statistics of all DSR tasks are now reported by the API, not just stats of tasks that are completed or in-progress. (OPSC-14873)
Restore Service
  • Amazon S3 destinations now support selecting a region from all currently available regions in the UI. (OPSC-14692)
  • Destination validation logic now happens in a DataStax agent. (OPSC-14611)
  • OpsCenter will now properly log exceptions from LDAP containing Unicode characters. (OPSC-14452)
  • Corrected an issue that caused the restore status to initially show 100% then reset to 0%. (OPSC-14995)
Monitoring
  • Improved the color scheme in the node status UI. (OPSC-12618)
Provisioning
  • Added information about upgrade jobs to the cluster workspace tooltip. (OPSC-13107)
  • Enlarged the SSH Private Key field in LCM UI to improve readability when entering SSH keys. (OPSC-13509)
  • 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 administrator 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)

OpsCenter 6.5.2 release notes

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

8 August 2018

Highlights

Implemented a fix for a critical bug that caused all active, compressed SSTable backups to be cleaned up unnecessarily, resulting in incomplete backups. Active, uncompressed SSTable backup files were unaffected.

See New features for more details.

Changes in 6.5.2

The following changes are included in this release.

Backup Service
  • Fixed a critical bug that caused all active, compressed SSTable backup files (.gz) to be cleaned up unnecessarily, resulting in incomplete backups. (OPSC-14880)

OpsCenter 6.5.1 release notes

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

5 July 2018

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.

Changes in 6.5.2

The following changes are included in this release.

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)

OpsCenter 6.5.0 release notes

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

17 April 2018

Highlights

  • Support for DSE 6.0
  • NodeSync Service
  • Lifecycle Manager improvements: support upgrading DSE versions on a datacenter or node within a supported release series; cloning and error validation in config profiles.

See New features for more details.

Changes in 6.5.0

The following changes are included in this release.

Core
  • Updated to the 1.6.2 version of the DSE driver. (OPSC-12624)
  • The agent can now be configured to enforce that certificate subjects match the opscenterd server. (OPSC-11806)
  • Opscenterd now only allows the TLSv1.2 protocol when HTTPS is enabled. (OPSC-11981)
  • Removed support for DSE versions older than 5.0. (OPSC-12784)
  • Improved default algorithm (rsa 2048) and hash (SHA256) for automatically generated self-signed TLS certificates. (OPSC-9941)
  • OpsCenter will fail to start if config_encryption_active is True and the system key file is missing. (OPSC-10284)
  • The first cluster that a role has permissions for is now automatically selected in the Cluster list of the Edit Role dialog. (OPSC-11759)
  • The default max heap size of the DataStax Agents has been increased to 1GB so that it better supports metrics collections in mid-large size clusters. The default heap size of opscenterd has also been increased to 2GB to better support the Repair Service. (OPSC-12313)
  • OpsCenter uses the G1 garbage collector instead of the Concurrent Mark-Sweep (CMS) garbage collector. (OPSC-12548)
  • OpsCenter and the DataStax Agent have added support for the new native_transport_* parameters introduced inside of cassandra.yaml in DSE 6.0. (OPSC-13181)
  • Tables in the OpsCenter schema are no longer created with compact storage because this feature has been removed in DSE 6.0. For more information, see the DSE upgrade guide (5.1 to 6.0) and the CQL commands for migrating from compact storage (DSE 5.1.x), or the DSE upgrade guide (5.0 to 6.0) and the CQL commands for migrating from compact storage (DSE 5.0.x) to CQL table format, depending on the DSE version. (OPSC-13527)
  • Fixed handling of API errors when enabling or disabling Alert Rules. (OPSC-12814)
  • Fixed timeout that caused the OpsCenter UI to fail to load. (OPSC-13053)
  • For DSE version 6.0 and later, the DataStax Agent no longer collects information about nodetool thriftstats in diagnostic tarball generation because it has been removed from DSE. (OPSC-13560)
  • Updated opscenterd to use CQL rather than HTTP to create Solr cores when necessary. (OPSC-12621)
  • The primary OpsCenter instance URL for failover can now be configured in the opscenterd.conf file. (OPSC-5409)
  • The cluster configuration and the DataStax Agents now have a configurable timeout for read timeout requests for both monitored and storage clusters through the DataStax Java driver. (OPSC-13919)
  • The agent now sends its agent_rpc_broadcast_address to opscenterd at the longtime_interval configured in address.yaml. This improves the agent's ability to auto connect to opscenterd when using dense nodes. (OPSC-14049)
Monitoring
  • Fixed an issue with scrolling to a highlighted activity during bulk operations in the Activities area of OpsCenter Monitoring. (OPSC-5651)
  • Added support for NodeSync metrics. (OPSC-10611)
  • New dropped message metrics have been added, whereas the TP: Dropped Paged Range Reads and TP: Dropped Request Responses metrics have been removed for DSE 6.0 and later. Several metrics regarding dropped messages have had their labels changed from TP: <message type> to Dropped Messages: <message type>. See Dropped Messages metrics. (OPSC-12777)
  • Additional thread pool metrics have been added for monitoring DSE 6.0 and later. (OPSC-12839)
  • Pagination in Activity Event Log now works correctly upon navigating back to first events page. New events can be fetched from server by clicking on Refresh from first page. (OPSC-4937)
  • Fixed an issue with Dashboard graph line colors when switching from a percentile graph in OpsCenter Monitoring. (OPSC-5258)
  • Updated metric descriptions to warn that key cache metrics only apply to pre-DSE 6.0 SSTables. (OPSC-13368)
Backup Service
  • OpsCenter restore will now recreate a graph if a graph was present at backup. (OPSC-11505)
  • Fixed an issue with restore that prevented additional indexes from being recreated when the restored table also included a Solr core. (OPSC-12756)
  • Graphs are now represented as top level objects in the restore workflow. Keyspaces that are part of a graph are now bundled together and are no longer shown individually when restoring a graph backup. (OPSC-12989)
  • Added an endpoint to the API that fetches a dictionary to the graphs and their associated keyspaces that are present in a particular snapshot. (OPSC-13007)
  • The AWS CLI feature for bulk uploading backups to Amazon S3 has been promoted from an OpsCenter Labs feature to an official production feature. Adjust your use_s3_cli configuration settings from the [labs] section to the [backups] section. (OPSC-13165)
  • Changed how the On Server commit log storage works. Commit logs are still initially moved into the backup_staging_dir, but after the commit logs have been sent to any other configured locations, the commit logs are moved to the directory specified by a backup_storage_dir defined in address.yaml. This approach should resolve a number of problems customers have encountered when restarting agents due to large numbers of On Server commit logs being reprocessed. See Configuring commit log backups for details. (OPSC-14073)
NodeSync Service
  • Added support for DSE NodeSync. (OPSC-12602)
  • NodeSync status has been added to the Nodes Services panels in OpsCenter Monitoring. (OPSC-13301)
  • Added a NodeSync Service section to enable NodeSync and view NodeSync status for a cluster's keyspaces and tables. (OPSC-13281)
  • Added a Best Practice rule to validate that the NodeSync Service is running on every cluster node. (OPSC-13064)
Repair Service
  • The parallel_tasks_update_interval configuration option has been added to the Repair Service. (OPSC-14252)
Best Practice Service
  • Added a Best Practice rule to validate that the NodeSync Service is running on every cluster node. (OPSC-13064)
Lifecycle Manager (LCM) Provisioning
  • Added the ability to clone Config Profiles in Lifecycle Manager. (OPSC-6428), (OPSC-12595)
  • Repository setup in Lifecycle Manager is now optional for those who manually configure and manage their package repos externally from LCM. (OPSC-12343)
  • LCM will now drain nodes (stops accepting writes and flushes memtables) before they are restarted. This provides additional safety and speeds up restarts. (OPSC-12581)
  • LCM UI edit config profile page can now display multiple field validation errors, and makes it easy to navigate between errors. (OPSC-12615)
  • LCM has the ability to upgrade DSE on existing (previously installed) datacenters and nodes when assigning a new config profile with a higher DSE version patch. Upgrade the DSE version in LCM within a minor patch release series in DSE versions 5.0.x, 5.1.x, and later. (OPSC-9570), (OPSC-12721)
  • LCM is now using React 15.6.2, up from React 0.14.8. (OPSC-12808)
  • Added concurrency options when executing a job on a cluster. (OPSC-5120)
  • When authentication is enabled, it is no longer necessary to enter credentials in the Job dialogs every time a job is run. After enabling authentication in a Config Profile, entering credentials at the cluster level is required only one time. Future credential changes are allowed. (OPSC-9439)
  • Added job events to job detail screen and made job detail node list more informative. (OPSC-9572)
  • Improved the ability of LCM to recover from some Java installation errors. (OPSC-10400)
  • LCM now includes all explicit node IP addresses when attempting to connect to the cluster for changing the default cassandra user password. This should fix password change for certain network setups. (OPSC-11096)
  • Job termination in LCM will now wait for PID file removal for about 10 seconds before giving up. This should reduce the frequency of the abort ending before Meld has had a chance to shutdown cleanly. (OPSC-11099)
  • LCM API requests can now return multiple errors. (OPSC-11131)
  • A Show/Hide field descriptions button has been added to LCM for those fields that have descriptions or tooltips available. (OPSC-12283)
  • LCM job event detail may now contain a 'source' field containing the property path of the data related to the event. (OPSC-12340)
  • Configuration data in LCM is now validated against the definition files. This ensures proper structure and value types for config profile data. (OPSC-12433)
  • Configuration profile data is now validated against field dependencies in the definitions. This prevents inconsistent configuration data. (OPSC-12434)
  • LCM error responses now consistently use the message key for error text. (OPSC-12438)
  • The LCM API base URL has changed from v1 to v2. For additional details regarding LCM API updates, see /en/upgrade/doc/upgrade/opscenter/upgrdTo6_5.html#upgrdTo6_5__LCMapiVersionChange in the OpsCenter Upgrade guide. (OPSC-12500)
  • All passwords in Lifecycle Manager now require double entry for confirmation. (OPSC-12563)
  • Added OpsCenter and Lifecycle Manager support for DSE version 6.0.0. (OPSC-12634)
  • Updated serial install logic in converged DCs to be specific to the Automatic concurrency level. (OPSC-12780)
  • Added definition to support DSE startup property -Dcassandra.force_3_0_protocol_version=true. (OPSC-12944)
  • Added ability to filter on null values to LCM API. (OPSC-12990)
  • Updated dependency versions. (OPSC-13141)
  • Updated Korma version to latest. (OPSC-13170)
  • Lifecycle Manager edit dialogs for SSH credentials, repositories, and clusters now clearly indicate whether passwords have been set and provide change options. Removing a stored password is now an explicit option; inadvertently removing a stored password is no longer possible. (OPSC-13239)
  • Rearranged the Edit Credential comment field to be displayed after required fields on LCM UI. (OPSC-13621)
  • Improved the UI in LCM config profiles by providing additional room for custom list items. (OPSC-13680)
  • The workload options in the LCM Add Datacenter dialog have been renamed to align with DataStax products: Solr is now DSE Search; Spark is now DSE Analytics. (OPSC-13758)
  • Updated the LCM UI and API to reflect the DSE 6.0 rename of rpc_address and broadcast_rpc_address to native_transport_address and native_transport_broadcast_address respectively. (OPSC-13843)
  • Fixed a bug in LCM node IP address inheritance for broadcast_rpc_address. It now defaults to thenative_transport_address (formerly rpc_address) setting, as indicated by the UI form. (OPSC-11970)
  • LCM will no longer inherit profile properties from a parent level when there are config profiles in a cluster topology for different DSE versions. Instead, the profile at the lowest topology level takes precedence and a warning is posted in the job events. (OPSC-12314)
  • Fixed a bug in LCM cluster import when there are datacenter- or node-specific config options. (OPSC-13546)
  • Fixed an issue with configuring Graph serializers in dse.yaml. (OPSC-13955)
  • Added warning about using a remote JMX connection without authentication. (OPSC-13982)
  • Fixed a bug where LCM UI form dialogs would reset values to original state while editing. (OPSC-14025)

Known and resolved issues for OpsCenter 6.x

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

The following are known issues that exist in OpsCenter 6.x 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, please contact DataStax Support for assistance.

  • Users may observe a large number of log messages about 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)
  • Failure to follow the required prerequisite instructions to install Oracle Java SE Runtime Environment 8 (JRE or JDK) before installing OpsCenter 6.0 on Ubuntu 16.04 results in installation of OpenJDK 9, which is not currently supported. (OPSC-10778)
  • For DSE versions earlier than 5.0.7, the 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 agent queries the system size_estimates table for a much 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)
  • (Applicable to OpsCenter version 6.1 or later only) For DSE versions 5.1 and later, slow query data is only available since the last time the DataStax agent was restarted. (OPSC-11702)
  • (Applicable to OpsCenter version 6.1 or later only) 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)
  • (Applicable to OpsCenter version 6.1 or later only) 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.
  • (Applicable to OpsCenter versions 6.0.x, 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)
  • Lifecycle Manager (LCM)
    • Lifecycle Manager is not currently compatible with DSE Transparent data encryption. See Encrypted DSE configuration values for more details. (OPSC-7529)
    • OPSC-8851, in 6.0.2, improved resiliency of Lifecycle Manager in situations where there is high latency between the OpsCenter daemon and nodes in the cluster. This release improves upon the problem; however, there are still known issues in high latency scenarios that will be addressed in a future release. (OPSC-9853)
    • DSE Graph properties (DSE 5.0.1+ only): 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)
    • (Applicable to OpsCenter 6.5 only) 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)
Known Issues Fixed in OpsCenter 6.0.8
Known Issues Fixed in OpsCenter 6.0.6
  • When modifying the Config Profile of an existing cluster in Lifecycle Manager, the Cluster Connection Settings in OpsCenter are now automatically updated after running a configure job. (OPSC-8544)
  • Fixed an issue where OpsCenter failed to retrieve the diagnostic tarballs from the agents if SSL was enabled between OpsCenter and the agents. (OPSC-10701)
Known Issues Fixed in OpsCenter 6.0.5
  • Fixed LCM repository authentication bug when special characters exist in credentials (as with most DataStax Academy usernames). (OPSC-10817)
Known Issues Fixed in OpsCenter 6.0.3
  • Any encrypted config values generated since Opscenter 6.0 (and prior to fix in 6.0.3) will need to be re-encrypted. (OPSC-10244).
  • Backups/Restores will not work with keyspace names longer than 32 characters on DSE 4.7 or 4.8. (OPSC-9563)
  • The Repair Service fails to auto-restart after a node is decommissioned. Manually starting the Repair Service resolves this issue. (OPSC-9244)
  • Some items in the Lifecycle Manager UI may not automatically update if they are modified outside of the current UI session; for example, via the API directly or in another UI session. If multiple users might be concurrently modifying the same cluster, please be sure to refresh the UI before making any changes. (OPSC-9306)
Known Issues Fixed in OpsCenter 6.0.2
  • g1-gc-opts in cassandra-env.sh are not immediately editable when using G1 garbage collection by default. To workaround this issue, change the garbage collector to something other than G1 and back again. (OPSC-9556)
  • Max heap size in cassandra-env.sh is not editable using the LCM UI. To workaround this issue, users can set the -Xmx and -Xms JVM properties directly via additional-jvm-opts further down on the cassandra-env.sh section in the Config Properties page. (OPSC-9546)
  • The use_tls setting in email alerts does not currently work as expected. Users can still configure email alerts to work with TLS-enabled servers by setting use_ssl=1 and use_tls=0. Please contact DataStax Support if you have any issues. (OPSC-9451)
  • Automatic definition file updates are not dynamically reloaded for new versions of DSE. If you see an error for "Unsupported or invalid version of DSE" in the UI, try restarting opscenterd. (OPSC-9468)
  • Some users may see intermittent job failures with an IncompleteRead error (OPSC-8851; see More Details)
  • The LCM UI has some rendering issues in older versions of Safari (<=8). The workaround is to use a newer version of Safari or another supported browser. (OPSC-9123)
Known Issues Fixed in OpsCenter 6.0.1
  • opscenterd fails to properly resolve relative symlinks to Java. (OPSC-9344; see More Details)
  • When installing an agent on a node for the first time, address.yaml is owned by the root user. The only OpsCenter functionality this affects directly is Automatic Failover, which will not work until ownership or permissions are updated. If the agent has previously been installed on the node, ownership is not affected. (OPSC-9336; see More Details)
  • S3 and Local FS backups fail for keyspaces leveraging the new Materialized Views feature in DSE 5.0. On Server backups are not affected. (OPSC-9328; see More Details)
  • Users must ensure tables that leverage the new User Defined Aggregates and User Defined Functions features in DSE 5.0 exist prior to running a restore. OpsCenter cannot automatically re-create these tables, but can successfully restore the data to existing tables. (OPSC-9261; see More Details)