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.1 changes pertinent to the release as noted in the DataStax OpsCenter Upgrade Guide. Configuration and other notable changes are provided in detail.
Known Issues
Important: Review the list of known issues before running a new OpsCenter version on a production DSE cluster.
Compatibility

To see which versions of DataStax Enterprise (DSE) are supported with OpsCenter 6.x, see the OpsCenter Compatibility chart.

OpsCenter 6.1.11 release notes

Release notes for the OpsCenter version 6.1.11 release.

8 October 2018

Highlights

  • Added two parameters to the [ldap] section of opscenterd.conf. These changes include support of LDAP searches for users without specifying an Organizational Unit (OU), plus adding the ability to follow LDAP referrals.

See New features for more details.

Changes in 6.1.11

The following changes are included in this release.

Core
  • Allows OpsCenter to support LDAP searches for users without specifying an Organizational Unit (OU). Also adds the ability to follow LDAP referrals. (OPSC-13384)

    The following flags were added to the [ldap] section of opscenterd.conf to manage the mentioned changes:

    enforce_single_user_search_result
    Returns an error when multiple entries are returned from a user search after all referrals (if applicable) are followed. Set to False if the user_search_base is not confined to one particular OU. Default: True.
    follow_referrals
    Sets whether the OpsCenter LDAP client should follow referrals. Active Directory typically does not follow referrals. Default: False.

OpsCenter 6.1.10 release notes

Release notes for the OpsCenter version 6.1.10 release.

26 September 2018

Highlights

  • Implemented numerous fixes and enhancements for backing up to Amazon S3.
  • Added multi-role support for LDAP authentication.
  • Statistics of all Distributed Subrange (DSR) tasks are now reported by the OpsCenter API, including completed, in-progress, and failed statistics.

See New features for more details.

Changes in 6.1.10

The following changes are included in this release.

Core
  • 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)
  • 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)
  • 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)
  • Reduced memory usage in opscenterd when requests are made to the DataStax Agent. (OPSC-15037)
  • Moved destination validation from OpsCenter to the DataStax Agent. (OPSC-14611)
Monitoring
  • Support added for new Read Coordination and Hint metrics added in DSE 5.0.12 (OPSC-12230):
    • 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
  • 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)
  • 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 where nodes were sometimes incorrectly indicated as DOWN in OpsCenter when they were actually UP. (OPSC-14299)
Backup Service
  • Added support to use system default credentials for Amazon S3 backups as described in Working with AWS credentials. (OPSC-5161)
  • Added proxy server support for Amazon S3 backup and restore. (OPSC-6978)
  • Backups to Amazon S3 locations now support Amazon S3 Transfer Acceleration. (OPSC-10271)
  • Upgraded Java AWS SDK to version 1.11.328. (OPSC-14454)
  • 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)
  • Fixed an issue where snapshots containing one or more SASI indexes could not be restored due to an invalid SSTable name exception during the validation checks. (OPSC-13314)
  • Fixed a small rendering issue in 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)
  • 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 a bug that could cause problems when restoring materialized views. (OPSC-14727)
  • 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)
  • 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 Amazon S3 destination after a restart 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 sent repeatedly to a destination during a backup. (OPSC-15009)
  • Fixed a memory leak in the Backup Service job execution cache. (OPSC-15015)
  • Reduced memory required when the Backup Service is taking a snapshot. (OPSC-15046)
  • Amazon S3 destinations now support selecting a region from all currently available regions in the UI. (OPSC-14692)
Repair Service
  • Omitted verbose C3P0 logging from the DataStax Agent log file. (OPSC-14176)
  • 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)
  • Statistics of all Distributed Subrange (DSR) tasks are now reported by the OpsCenter API, including completed, in-progress, and failed statistics. (OPSC-14873)
  • Fixed a bug for Distributed Subrange Repair (DSR) to honor the max_parallel_repairs property, which was remaining at a value of 1 regardless the specified value. (OPSC-14947)
Provisioning
  • Added tooltips for several custom URLs to provide examples of what Lifecycle Manager (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)
  • Fixed an issue where column names overlapped in the key_provider edit dialog in LCM. (OPSC-10990)
  • Enlarged the ssh-key field in LCM to improve readability when entering SSH keys. (OPSC-13509)
  • 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)
  • Modified the locations that LCM uses to traverse the cluster model when determining the SSH management port. (OPSC-14258)
  • Improved error message returned when the $JAVA_HOME environment variable is invalid. (OPSC-14390)
  • Fixed an issue where LCM jobs would fail to terminate when aborted. (OPSC-14410)
  • Disallow LCM to import a cluster when opscenterd is not fully communicating with a cluster. (OPSC-13367)
Dashboard
  • Fixed an issue where sparklines in the cluster Overview pane would initially load, but not update. (OPSC-13913)
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)

OpsCenter 6.1.9 release notes

Release notes for the OpsCenter version 6.1.9 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.1.9

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.1.8 release notes

Release notes for the OpsCenter version 6.1.8 release.

25 July 2018

Highlights

Implemented a fix for rolling repairs so that a new repair job starts automatically if the current job fails. This fix applies to all repair job types (incremental, subrange, and distributed subrange).

Note: This issue was a regression that is not present in previous versions of OpsCenter 6.1.x.

See New features for more details.

Changes in 6.1.8

The following changes are included in this release.

Repair Service
  • Restore "last repaired" timestamps to the Repair Service UI, which were previously missing. (OPSC-14399).
  • Protect distributed subrange temporary files from being deleted when DataStax agents start. (OPSC-14719).
  • 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).
  • Prevent duplicate distributed subrange tasks (OPSC-14769).

OpsCenter 6.1.7 release notes

Release notes for the OpsCenter version 6.1.7 release.

18 June 2018

Highlights

Implemented DSR (Distributed Subrange Repair) as an alternative implementation of subrange repairs within the OpsCenter Repair Service, intended to better scale for large clusters. See Enabling distributed subrange repairs.

See New features for more details.

Changes in 6.1.7

The following changes are included in this release.

Core
  • Sensitive password fields in the cluster configuration are no longer returned by the API. (OPSC-4361)
  • Added a dialog to OpsCenter UI prompting the user to refresh the browser when the underlying OpsCenter server version has changed. (OPSC-11254)
  • Fixed an issue where nodes would be incorrectly marked as DOWN when they are in fact UP after being added again to the cluster. (OPSC-13408)
  • Fixed an issue where opscenterd would not always properly update a node's UP/DOWN state based on the number of peers that report the node to be down. (OPSC-13909)
  • Fixed a bug where dialogs in OpsCenter would reposition incorrectly when the dialog contents changed size. (OPSC-13914)
Monitoring
  • 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.1.x installations. Metric data collected prior to deploying the fix will remain invalid. (OPSC-13657)
  • Fixed an issue with the node name and IP background color in the Ring view. (OPSC-10635)
Backup Service
  • Removed an outdated 3rd-party URL used in an SSTableloader max heap size error message. (OPSC-13794)
  • Fixed an issue that could cause backup SSTable cleanup on a destination to miss some files. (OPSC-13223)
  • Fixed an issue with backup S3 and local destination file sync that would abnormally halt when errors occurred during the sync. (OPSC-13957)
  • Fixed a bug that in some cases prevented restore of backups taken from prior versions of OpsCenter. (OPSC-14034)
  • Fixed a bug that prevented restore of a point-in-time (PIT) backup if the On Server destination was missing the snapshot files. (OPSC-14370)
  • Fixed a bug that caused errors in the agent log when syncing commit logs to destinations. (OPSC-13645)
  • Corrected an issue with truststore argument to SSTableloader during restore. (OPSC-13686)
  • Optimized backup file comparison synchronization. (OPSC-14559)
Best Practice Service
  • Fixed an issue where the Best Practice Service would flag multiple networks in the network check when there is only one network that is not a loopback device. (OPSC-13190)
Performance Service
  • Fixed a bug in the Table view of Performance Service where the Node grid would not render. (OPSC-13959)
Repair Service
  • Implemented the DSR (Distributed Subrange Repair) feature, which is an alternative implementation of subrange repairs for the OpsCenter Repair Service. DSR is designed to scale for larger clusters by distributing more work to the agents. (OPSC-13531)
  • Added the use_distributed_subrange_repair config option to the Repair Service for running distributed subrange repairs (DSR). (OPSC-13538)
  • The Repair Service no longer creates or uses a clustername.json persistence file. (OPSC-13306)
  • Replaced in-memory repair tasks management with a SQLite database to avoid OOM errors when generating a large number of subrange tasks. (OPSC-13543)
  • Switched to streaming json parsing/generation of large HTTP responses when gathering token ranges from agents as well as generating keyspace metadata for the UI to avoid generating large data structures in-memory. (OPSC-13543)
  • Fixed a bug where repair service would resume prematurely if a cluster topology change was longer than the configured resume timeout. (OPSC-12165)
Lifecycle Manager (LCM) Provisioning
  • Improved the usability of the Rack field in the LCM Add/Edit Node dialog by adding an autocomplete combo box to retain previously entered rack names for selection. (OPSC-13205)
  • Tabbing behavior in the LCM UI has been improved. (OPSC-13204)
  • Fixed a bug in LCM cluster import when there are datacenter- or node-specific config options. (OPSC-13546)

OpsCenter 6.1.6 release notes

Release notes for the OpsCenter version 6.1.6 release.

30 January 2018

Highlights

  • Lifecycle Manager can now display up to 300 nodes per datacenter, where previously it was only 50.
  • The LCM link in the OpsCenter monitoring navigation sidebar is unavailable for users who do not have the Admin role for OpsCenter authentication.

See New features for more details.

Changes in 6.1.6

The following changes are included in this release.

Core
  • Updated project dependencies to no longer be susceptible to CVE-2016-1000031. (OPSC-13404)
  • The Cluster Health pane now properly sorts datacenter names. (OPSC-11438)
  • The LCM link in the OpsCenter monitoring navigation sidebar is unavailable for users who do not have the Admin role for OpsCenter authentication. (OPSC-12303)
  • The repair_service_subrange.json and repair_service_incremental.json job persistence files have been added to the diagnostic tarball. (OPSC-12887)
  • Added an error message to specifically identify JMX timeouts and inform the user about the agent config parameter than can be adjusted to deal with it. (OPSC-12679)
  • An updated MINA version now ships that alleviates a CPU issue associated with LDAP. (OPSC-12946)
  • Fixed an issue with authentication and LDAP (configured with anonymous bind), where invalid logins prevented valid LDAP logins from working unless opscenterd was restarted. (OPSC-13045)
  • Fixed a bug in the Agent Status View that displayed blank rows when there were large numbers of agents. (OPSC-13351)
  • Updated secure connections from opscenterd to the agent to use TLS 1.2 instead of TLS 1.1 due to stricter crypto policies in the latest JDK versions. (OPSC-13710)
Monitoring
  • Changed the behavior in the OpsCenter UI so that if an alert is tied to a metric that no longer exists (or does not exist due to a failed definitions update), the UI will ignore the corresponding alerts and give an option to manually delete the alert rules instead of outright deleting them. (OPSC-13382)
Backup Service
  • Improved logging around some restore backup error cases. (OPSC-12862)
  • Fixed an issue that prevented synced snapshot events from appearing in the restore list. (OPSC-13360)
  • Improved the speed at which local backup destinations compute files that need to be synced. (OPSC-13410)
Best Practice Service
  • Fixed a rendering bug in the Best Practice rule details dialog. (OPSC-13334)
Repair Service
  • Improved memory usage when loading saved subrange repair state. (OPSC-13317)
  • Fixed an issue with Repair Service subrange task size creation that caused extremely high data sizes to be repaired. (OPSC-13310)
  • Fixed logic for comparing \[repair_service].max_pending_repairs to running repairs when using DSE 5.0+. (OPSC-13392)
  • Fixed repair service subrange repairs ignoring mixed case keyspaces when DSE version is earlier than 5.0.7. (OPSC-13637)
Lifecycle Manager (LCM) Provisioning
  • Trailing slash is now optional for LCM API endpoint URLs. (OPSC-5868)
  • LCM does not allow running a configure job before a successful install job. LCM now enforces running an install job as a prerequisite to running a configure job. (OPSC-11228)
  • LCM gives better error messages when the downloaded JRE/JCE archives cannot be extracted. (OPSC-13327)
  • The LCM Config Profile editor now displays default values for dictionary grid views when no value has been entered by a user. (OPSC-10216)
  • Fixed a race condition in LCM's usage of SQLite that lead to rare SQLITE_BUSY and foreign key errors. (OPSC-12349)
  • LCM automatically populates the ssl_truststore and ssl_truststore_password fields in the Edit Cluster Connections dialog using the corresponding values from ssl_keystore and ssl_keystore_password. The My Keystore and Truststore are the same check boxes have been removed from the Connect to Existing Cluster and Edit Cluster Connections dialogs. (OPSC-12910)
  • Fixed a bug that prevented proper alignment of ellipses in the Jobs page of LCM. (OPSC-13192)
  • Fixed a bug in the LCM UI where the DSE Version list on the Add Config Profile page did not sort DSE versions correctly (descending order). (OPSC-13212)
  • Fixed a bug where importing a non-GPFS snitch cluster into LCM would create an error event in the node events but would not fail the job. The job now properly fails with the unsupported snitch event. (OPSC-13233)
  • Fixed an LCM UI bug where adding and subsequently removing custom dictionary entries on edit config profile would disallow closing a dialog. (OPSC-13342)
  • Fixed an agent install bug where only approximately 50 nodes were getting installation status updates. (OPSC-13350)
  • Disabling client-to-node encryption from LCM now properly updates the related cluster.conf file. (OPSC-13460)
  • Fix a bug where CQL password changes fail when authentication is enabled and rpc address is 0.0.0.0. (OPSC-13475)
  • Fixed a bug in LCM URL redirects so that they retain query string parameters from the original URL. Optimized related-resources links by avoiding redirects. (OPSC-13508)
  • Lifecycle Manager can now display up to 300 nodes per datacenter on its UI; previously it was 50. (OPSC-13508)
  • Fixed an issue when setting SPARK_MASTER_LOG_DIR from LCM. (OPSC-13516)

OpsCenter 6.1.5 release notes

Release notes for the OpsCenter version 6.1.5 release.

14 November 2017

Highlights

  • Added support for Percent Data Repaired (previously SSTables Repaired) metrics at the node and table levels for DSE versions 5.0.6 and later.
  • LCM now supports Amazon Linux AMI 2016.09 and 2017.03. (OPSC-6582)

See New features for more details.

Changes in 6.1.5

The following changes are included in this release.

Core
  • XHRStream communications failover automatically to long polling after 1 minute. (OPSC-9454)
  • Removed tooltip question marks from the tab order sequence in the Edit Cluster Connections dialog in OpsCenter Monitoring. (OPSC-11022)
  • Fixed related resources links for jobs and nodes associated with a cluster. (OPSC-12972)
  • Improved layout on a few OpsCenter Monitoring pages and dialogs to avoid excessive scrollbars. (OPSC-12995)
  • Fixed a layout issue with cluster seed text area (expanded the Enter host or IP box in the Connect to Existing Cluster dialog). (OPSC-4350)
  • Fixed an issue where opscenterd was unnecessarily migrating table metadata on every restart. (OPSC-12001)
  • Fixed a rendering bug causing harmless browser console messages when opening the Node Details dialog. (OPSC-12997)
  • Fixed a bug with rendering of sparklines on the global OpsCenter Monitoring dashboard. (OPSC-13038)
  • Fixed timeout that caused the OpsCenter UI to fail to load. (OPSC-13053)
  • Fixed a bug with the Cluster Connections Settings dialog rendering properly when resized smaller. (OPSC-13116)
  • Fixed a bug where a secondary OpsCenter instance would generate an invalid link to the primary OpsCenter when https is enabled. (OPSC-13140)
  • Fixed rendering edge case in agent grid affecting horizontal scrolling in narrow windows. (OPSC-13262)
Monitoring
  • Added support for Percent Data Repaired (previously SSTables Repaired) metrics at the node and table levels for DSE versions 5.0.6 and later. (OPSC-12982)
  • Moved the metrics dropdown tooltip to the left to avoid occluding the scrollbar. (OPSC-13077)
Backup Service
  • Improved error message when destination pre-test fails. (OPSC-13159)
  • Add messages to detail the agent activity during a backup. (OPSC-13242)
  • Fixed a UI bug when reporting backup progress on large clusters. (OPSC-4430)
  • Fixed a bug with header spacing in the restore from backup list. (OPSC-5778)
  • Updated the backup report dialog to include empty tables because their schema is backed up. (OPSC-12703)
  • Fixed a bug where only a subset of keyspaces were shown in the Restore from Backup dialog keyspace selector. (OPSC-13010)
  • Improved resize behavior of Restore from Backup dialog. (OPSC-13049)
  • Corrected an issue that prevented restores to DSE 4.8 clusters with optional client-to-server ssl. (OPSC-13155)
  • Corrected an issue where scheduled backups with a cleanup policy would always fail if a retry sync was triggered. (OPSC-13234)
Repair Service
  • Increased Repair Service tokenranges_partitions default value to 2^20, matching what DSE uses for its Merkle tree depth in CASSANDRA-5263. (OPSC-12901)
  • Fixed an issue where repair service pausing event log messages were generated when the repair service wasn't running. (OPSC-13002)
Lifecycle Manager (LCM) Provisioning
  • LCM now supports Amazon Linux AMI 2016.09 and 2017.03. (OPSC-6582)
  • Improved the error message when an LCM password change prevents connecting to CQL. (OPSC-12535)
  • LCM now allows debug log to be disabled through the logback.xml configuration. (OPSC-13109)
  • Added a tooltip for the advanced-jvm-options field in the jvm-options UI of LCM Config Profiles. (OPSC-13122)
  • Added a tooltip for the endpoint snitch in the cassandra.yaml UI of LCM Config Profiles. (OPSC-13123)
  • Added a 30 second timeout for HTTP requests in Meld. Among other potential HTTP endpoint issues, this addresses LCM jobs hanging while trying to download the JDK. (OPSC-13134)
  • The LCM UI now explicitly defaults nodes' rack field to rack1. (OPSC-10814)
  • LCM now sets secure permissions on the directories and files it creates for signing and storing SSL certificates. (OPSC-11793)
  • LCM now gives a better error message when SSL certificate creation fails due to clock drift on the target node. (OPSC-12321)
  • Fixed charset issue resulting in superfluous non-ASCII characters displaying in the LCM UI. (OPSC-12932)
  • Fixed a bug on LCM UI where a datacenter name would erroneously be displayed on the Run Job dialogs for a cluster. (OPSC-12965)
  • Fixed a bug in LCM where cluster imports were always failing during the supported platform check. (OPSC-13218)
  • LCM will now retry the Oracle JRE download twice if it has a connection or timeout error. (OPSC-13293)

OpsCenter 6.1.4 release notes

Release notes for the OpsCenter version 6.1.4 release.

24 October 2017

Highlights

See New features for more details.

Changes in 6.1.4

The following changes are included in this release.

Core
  • Fixed an issue with agent stomp connections on nodes with two network adapters. (OPSC-13016)
Lifecycle Manager (LCM) Provisioning
  • Fixed issue where Oracle no longer hosts the version of Java that LCM attempts to download by default. (OPSC-13332)

OpsCenter 6.1.3 release notes

Release notes for the OpsCenter version 6.1.3 release.

21 September 2017

Highlights

  • Added an OS supported platform check for DSE installs in LCM.
  • Added a Labs feature to use the AWS CLI instead of the AWS SDK when bulk loading backups to Amazon S3. Significant performance impact!
  • Added the ability to sync a snapshot to a destination for On Server backups.

See New features for more details.

Changes in 6.1.3

The following changes are included in this release.

Core
  • Timeouts for all API calls are proportional to default_api_timeout setting. (OPSC-12206)
  • Added a Hide and Show toggle for the status panels on the Nodes page. (OPSC-12424)
  • Fixed memory leak in node list tooltips. (OPSC-12614)
  • Fixed an issue where LDAP sockets remained open after failed login attempts. (OPSC-12656)
  • Now show loading indicator while service panels initialize. (OPSC-12714)
  • Fixed bug where service panels would stay in error state after server restart. (OPSC-12749)
  • Fixed broken View in List link in cluster ring popup menus. (OPSC-12786)
  • Fixed stack trace when details requested for a node with agent down. (OPSC-12788)
  • Fixed an issue where the DataStax Agent would stop responding due to a bug during configuration changes. (OPSC-12921)
Backup Service
  • Added the ability to sync a snapshot to a destination for On Server backups. (OPSC-12574)
  • Added the ability to auto retry syncing backups to destinations. (OPSC-12575)
  • Improved the resiliency of the DataStax Agent during backups. (OPSC-12576)
  • Added a configuration option to use the AWS CLI (Command Line Interface) scripts for bulk uploading rather than the S3 API when backing up to Amazon S3. Using the Amazon S3 cli is a labs feature that must be enabled. (OPSC-12688)
  • Made the destination verification timeout configurable. (OPSC-10409)
  • Local FS destinations for Backup Service now respects the throttling parameter. (OPSC-12174)
  • Fixed scrolling on dialog content when browser window is small. (OPSC-12562)
  • Corrected an issue where a failed backup could result in excessive error messages in the opscenterd log. (OPSC-11122)
  • Backup process is more resilient to lost progress messages. (OPSC-12758)
  • Contains fix for leaking file descriptors when the backup service takes a snapshot. (OPSC-12900)
  • Fixed an issue where the restore rate was not displaying in the ui. (OPSC-12974)
  • Fixed an issue where having more than one scheduled backup would cause the ui list to display nothing. (OPSC-12873)
Repair Service
  • Repair Service will now switch away from the Status tab when it is detected to be inactive. (OPSC-11223)
  • Fixed an issue where leaving the repair service status open for longer periods of time could slow down the UI. (OPSC-12833)
  • Fixed an issue with Out of Memory errors in opscenterd on the Repair Service Status page by removing the bottom Repair Tasks panel and optimizing the repair-status API endpoint. (OPSC-12857)
  • Fixed a bug that indicated the incorrect agent minimum version. (OPSC-12896)
Performance Service
  • Fixed column sorting in the Slow Queries page of the Performance Service. (OPSC-11704)
Best Practice Service
  • Best Practice Rule for Secondary Index Cardinality no longer fails for system keyspaces. (OPSC-6913)
Lifecycle Manager (LCM) Provisioning
  • Improved a meld error concerning PID file permissions to be more informative. (OPSC-12537)
  • LCM now performs a check during install and import jobs to ensure the OS platform is supported for the version of DSE being installed. This behavior can be overridden with the new disable_platform_check config option in the lifecycle_manager section of opscenterd.conf. (OPSC-11592)
  • Corrected a bug that could cause comments to fail to display in LCM cluster, datatacenter, and node edit pages. (OPSC-12558)
  • Fixed a rendering issue with user_defined config profile editor in LCM. (OPSC-12559)

OpsCenter 6.1.2 release notes

Release notes for the OpsCenter version 6.1.2 release.

26 July 2017

Highlights

  • Developed new optimizations for making subrange repair metadata processing more performant for large and/or dense clusters. (OPSC-11976)
  • LCM ensures that the correct version of DSE is present before modifying the target node in configure jobs. (OPSC-12503)

See New features for more details.

Changes in 6.1.2

The following changes are included in this release.

Core
  • Changed the UI labeling from deleting a cluster to disconnecting a cluster in the Edit Connection Settings dialog to make it clear that the clusters themselves are not actually deleted. (OPSC-10654)
  • Removed the redaction of usernames from agent logs. Passwords continue to be redacted. (OPSC-10285)
  • Combined the Services and Operations panels in the Nodes page. (OPSC-12270)
  • Changed the UI labeling from deleting a cluster to disconnecting a cluster in the Edit Connection Settings dialog to make it clear that the clusters themselves are not actually deleted. (OPSC-10654)
  • Added the ability to select or deselect all permissions for OpsCenter roles. (OPSC-11757)
  • Fixed an issue that prevented CQL Solr queries from being reflected in OpsCenter metrics. (OPSC-12071)
  • Fixed issue with agent connections in some failover situations. (OPSC-11292)
  • When the listen_address field in cassandra.yaml file is left blank, OpsCenter agents now default to the same listen address as DSE. (OPSC-12246)
  • Fixed a bug where OpsCenter failed to display a correct representation of the cluster state after an LCM job restart. (OPSC-12376)
  • Corrected an issue where the agent was using a legacy method to authenticate with DSE. (OPSC-12560)
  • Changed the icon for the Last Install Status Pending state in the Agent Status view. The icon is now differentiated from the Installing icon. (OPSC-11229)
Monitoring
  • Added ClientRequest metrics for various types of unsuccessful reads and writes. (OPSC-12186)
  • OpsCenter metrics storage can now be disabled by using the bypass_dse_metrics_storage configuration option in cluster_name.conf or address.yaml. (OPSC-12235)
  • Fixed a bug that could cause the ring for a vnode cluster to display with a large gap. (OPSC-12426)
  • Fixed an issue that prevented the selection of day for the duration of an alert. (OPSC-12351)
  • Fixed an issue where a change to the percentile of an alert would not take effect without restarting opscenterd. (OPSC-12352)
Backup Service
  • Fixed issue where backup report dialog would display date and time of backup in the local time zone of the browser rather than UTC. (OPSC-7261)
  • Zipped version of backup files are now automatically deleted after being uploaded to destinations. (OPSC-9131)
  • Corrected an issue that required the user to provide a value for local_interface when configuring agents for use on dense nodes. (OPSC-11777)
  • Improved commit log status display when no commit logs have been archived. (OPSC-12062)
  • There were occasional problems when restoring a backup related to schema changes. This was improved by better logic around waiting for schema agreement. (OPSC-12231)
  • Fixed issue where S3 upload failed with message "resetting to invalid mark". (OPSC-12278)
  • Fixed issue where Backup Service would incorrectly report a restore as failed due to a misreading of the bulk load status. (OPSC-12317)
  • A bug in scheduling was found and fixed where a scheduled job (notably backups) would be rerun almost immediately after the second time it was executed. (OPSC-12205)
Repair Service
  • Suppress the Repair Won't Finish In Time alert when elapsed throughput is below the configured min_throughput property value. (OPSC-12207)
  • Developed new optimizations for making subrange repair metadata processing more performant for large and/or dense clusters. (OPSC-11976)
Lifecycle Manager (LCM) Provisioning
  • Updated SSH errors to be more helpful. (OPSC-10849)
  • Updated unexpected password prompt errors to have a more helpful error message. (OPSC-12484)
  • Added support to detect and log when openssl and keytool binaries are missing on the LCM node. (OPSC-12210)
  • Improved error message around bad LCM decryption keys. (OPSC-12306)
  • Added human readable message under the message field for API errors. (OPSC-12498)
  • If the openssl or keytool executables are missing, this will be reported in the LCM UI as a job event. (OPSC-12519)
  • Eliminated SQLITE_BUSY errors when using LCM. (OPSC-11885)
  • LCM ensures that the correct version of DSE is present before modifying the target node in configure jobs. (OPSC-12503)
  • Corrected a bug that could cause comments to fail to display in LCM cluster, datatacenter, and node edit pages. (OPSC-12558)

OpsCenter 6.1.1 release notes

Release notes for the OpsCenter version 6.1.1 release.

12 June 2017

Highlights

  • Many helpful content additions to the diagnostic tarball for better troubleshooting, along with an improved customer experience.
  • Support for HTTP Strict Transport Security (HSTS).
  • Added SSL truststore configuration options for the agent.
  • Summary panels for Services and cluster health have been added to the Nodes page for a quick view of status and fast access to each Services section.

See New features for more details.

Changes in 6.1.1

The following changes are included in this release.

Core
  • Added some additional files (logback.xml files to /opscenterd and /dse, log4j.properties to /agent, jvm.options and commitlog_archiving.properties to /cassandra, and /etc/hosts) to diagnostic tarball contents. Also fixed an issue with a missing trailing slash that caused agent diagnostic files to be filed directly under the /conf folder instead of the /agent subfolder. (OPSC-11611)
  • Agent status information is now included in the diagnostic tarball. (OPSC-7277)
  • When reporting a failure to generate a diagnostic tarball due to a lack of available disk space, the amount of space required, the amount of space available, and the working directory for diagnostic tarball generation is now clearly logged. (OPSC-5959)
  • The diagnostic tarball no longer creates a file containing an error message rather than a directory if a node's diagnostic tarball could not be downloaded. A file name agent_requests.json is now included that indicates the success or failure of retrieving diagnostic tarballs from each node. (OPSC-6258)
  • Whenever possible, any current information from the Best Practice Service is now included in the diagnostic tarball. (OPSC-4956)
  • The agent now re-uses an existing connection to DSE when gathering some diagnostic tarball output rather than forking additional cqlsh processes. (OPSC-7081)
  • The agent will retry hung connection attempts to DSE nodes. (OPSC-11935)
  • Summary panels with status and links to the Services have been added to the Nodes page. (OPSC-12138)
  • Selecting a keyspace is now optional when performing a cleanup, compact, or flush node operation. This feature is not backwards-compatible with agent versions earlier than 6.1.1. (OPSC-510)
  • Added truststore settings to agent configuration for both monitored and storage clusters. (OPSC-8003)
  • Cleaned up logging on opscenterd shutdown. (OPSC-8278)
  • Selecting NetworkTopologyStrategy while editing a keyspace in the OpsCenter Data section now populates the datacenter replication factor parameters with the datacenters in the cluster topology. Any previously specified replication factor values for a given datacenter parameter will be reused. Assigning a replication factor of 0 to a datacenter parameter excludes replication on the datacenter. (OPSC-10680)
  • Included change details in audit log messages for updates to role permissions. (OPSC-10929)
  • Added summary information about running Services to the cluster landing page. (OPSC-11247)
  • Removed repetitive log message 'INFO: Node 172.31.11.1 has multiple tokens (vnodes). Only one picked for display. (MainThread)'. Only affects vnode clusters. (OPSC-11557)
  • Added the X-XSS-Protection to content responses to enable the XSS auditor in various supported browsers. (OPSC-11845)
  • Fixed a bug where opscenterd would automatically encrypt values in its configs if a system key was present, whether config encryption was enabled or not. (OPSC-7152)
  • Allow access to the left navigation, including LCM, when there's only one cluster configured and OpsCenter cannot connect to it. (OPSC-11101)
  • Provide clear messages in the diagnostic tarball when using DSE 5.0 or greater that the removal of Thrift has also removed the use of cassandra-cli. (OPSC-11239)
  • Improve messaging around timeouts when logging in via LDAP. (OPSC-11396)
  • New OpsCenter roles now default to having no permissions for any clusters. (OPSC-11685)
  • The DataStax Agent may now use different passwords for the keystore and truststore. (OPSC-11767)
  • Fixed a bug when resuming monitoring after a rolling restart. (OPSC-12095)
  • Optimized requests for Service status while viewing a service detail page. (OPSC-12136)
  • Improved error handling logging around HTTP calls to the agent. (OPSC-12143)
  • Improved handling of separate storage cluster. (OPSC-8235)
  • Attempting to log in without specifying a username now gives a proper HTTP Unauthorized response instead of a 500 error response. (OPSC-9469)
  • If OpsCenter authentication is enabled, users who do not have View Schema permission in their assigned role are not allowed to view schema data in the Data area of OpsCenter monitoring. OpsCenter presents an informational message that instructs users to contact their OpsCenter administrator for access. (OPSC-11319)
  • Redacted passwords from debug log statements in WrappedDriver. (OPSC-11448)
  • Fixed a bug during agent install that is triggered when no events have been reported. (OPSC-11640)
  • Updated solr-cores and range-list routes in agent to address intermittent errors. (OPSC-11674)
  • Fixed agent processing of KMIP errors for alerts. This was causing log spam in the agent and was preventing other real-time information from being reported to OpsCenter. (OPSC-11972)
  • Fixed a bug where the dashboard would not display when non-ASCII characters are present in a username. (OPSC-12064)
  • Fixed an issue where requests would timeout when using AD 2012 with SSL. (OPSC-11995)
Monitoring
  • Added Speculative Retries metrics to OpsCenter monitoring. (OPSC-11503)
  • Added Coordinator Read Latency table metric. (OPSC-11509)
  • Clarify the units in several 'TP: Dropped X' metrics. (OPSC-11714)
Backup Service
  • Improved performance when displaying updates in the restore status dialog. (OPSC-1498)
  • Added support for folders and subfolders to Amazon S3 buckets used for backups and restores. (OPSC-6845)
  • Agent configuration now validates that backup_staging_dir is set to an absolute path. (OPSC-9393)
  • Fixed sorting of scheduled backups. (OPSC-11007)
  • Horizontal scroll has been added to the OpsCenter Services section when the browser window is too small. (OPSC-11144)
  • Improved the error message during certain backup failure cases. (OPSC-11733)
  • Fixed the display of the list of backups presented after adding a backup location. (OPSC-11933)
  • Fixed an issue where backups to S3 would stop without logging an error. (OPSC-12188)
  • Fixed an issue that caused the destination dialog to appear multiple times when restoring from an ad hoc S3 backup. (OPSC-11569)
  • Removed checks preventing users from restoring backups across major versions. This restriction was in place because earlier but no longer supported versions of Cassandra did not allow this. It is now possible to restore backups from any version of Cassandra that is compatible for upgrading. (OPSC-11766)
Repair Service
  • Increased accuracy when computing repair service job throughput. (OPSC-11171)
  • Fixed a NullPointerException in agents when repair service was running and the cluster was rebalanced. (OPSC-11668)
  • Repair Service settings shows calculated time to completion separately from the setting's input field. (OPSC-11985)
  • Clarified display of total repair attempts in the repair status page. (OPSC-12004)
  • Fixed repair to not use keyspaces in the ignored_keyspace property when computing the maximum number of repairs that can run in parallel. (OPSC-12045)
  • Fixed an issue in the repair service where restarting OpsCenter would disable the repair service. (OPSC-12237)
Performance Service
  • Fixed column sorting in the Slow Queries page of the Performance Service. (OPSC-11704)
  • Performance Service in OpsCenter can only be configured when at least one agent is connected. The OpsCenter api now returns an empty array instead of an empty object for /perf/config when no agents are connected. (OPSC-11267)
Best Practice Service
  • Best Practice Rule for Secondary Index Cardinality no longer fails for system keyspaces. (OPSC-6913)
  • Fixed column sorting in the Slow Queries page of the Performance Service. (OPSC-11704)
Lifecycle Manager (LCM) Provisioning
  • LCM now warns users that config-encryption is not supported. (OPSC-7616)
  • LCM now tries to assign one seed per rack, two seeds per datacenter, and three seeds for each cluster. (OPSC-11160)
  • LCM proceeds with jobs when a become-password is set in the machine-credential even if the target does not prompt for a sudo password, rather than generating a misleading meld-not-started error. (OPSC-11216)
  • Updated the Java download UI in LCM to reflect new Oracle URL structure. Also added tooltips to assist users with completing Java Setup fields for Config Profiles. (OPSC-11418)

OpsCenter 6.1.0 release notes

Release notes for the OpsCenter version 6.1.0 release.

18 April 2017

Highlights

  • Support for DSE 5.1.
  • Revamped Repair Service! Smarter and more performant repair with real visibility into the progress and results of the repair process.
  • DataStax agent improvements: Backward compatibility with the installed OpsCenter version, which provides flexibility with the timing of upgrading agents; improved Agent Status view; and access to the DataStax Agent API in a Swagger UI console.

See New features for more details.

Changes in 6.1.0

The following changes are included in this release.

Core
  • The Hadoop workload type has been removed from the Datacenter dialog in LCM. Support for Hadoop has been deprecated. (OPSC-10466)
  • Changed criteria when the Analytics filter is used to constrain the nodes that provide data for a given graph. Previously only Hadoop nodes were considered when using this filter, but now only Spark nodes are considered. (OPSC-9562)
  • Added the swagger_enabled config option to address.yaml that exposes the DataStax Agent API in a Swagger UI console. (OPSC-10337)
  • Added an appropriate error when an incompatible route is called. (OPSC-9905)
  • Updated agent status to appropriately indicate incompatibility and limitations. (OPSC-9908)
  • If an agent's version will not permit a Best Practice Rule to run, a warning is shown when configuring the rule's schedule. (OPSC-9911)
  • OpsCenter added support for messaging latency metrics when monitoring DSE clusters from versions 5.1 and later. (OPSC-10093)
  • Added the ability to configure static JVM options in a jvm.options file within Lifecycle Manager config profiles for DSE clusters version 5.1.0 and later. The options were moved from cassandra-env.sh to jvm.options. See Configuring JVM options in LCM. (OPSC-10101)
  • The set of available cipher suites for TLS encryption of communication between the agent and DSE has been expanded to support the set of ciphers supported by the Java platform. This matches a similar change in Apache Cassandra™, which allows for negotiation of the strongest common cipher suite. (OPSC-10187)
  • Added support for DSE Integrated Authentication for JMX in DSE 5.1. See Configuring a JMX Connection using LCM. (OPSC-8752)
  • Added metrics for monitoring DSE Graph in OpsCenter. (OPSC-10180)
  • The banner that notifies users of agent issues no longer includes agent version mismatches that do not impact features. Incompatible version mismatches still appear in the banner. (OPSC-10327)
  • Agent Upgrade information is now presented in a text block above the agents status table. Agents can be upgraded by clicking the Upgrade Agents button. (OPSC-10615)
  • The Agent Version is now listed in the Agent Status tab. (OPSC-10616)
  • Agents with incompatible versions are now listed as problems in the agent status notification banner. (OPSC-10617)
  • Definitions files have been moved out of configuration directories (/etc/opscenter for package installs; install_location/conf for tarball installs.) The new locations are /var/lib/opscenter/definitions and install_location/definitions, respectively. This will be transparent to the majority of users. (OPSC-6704)
  • Added version prefix to agent API URIs. (OPSC-7531)
  • Removed path_to_installscript option from the [agents] section of opscenterd.conf. That option will now be ignored. The agent install process is now internal to Opscenter, and no external script is necessary. (OPSC-9119)
  • Moved agent-to-opscenter SSL settings from JVM_OPTS in the agent startup script to address.yaml. SSL settings in JVM_OPTS will continue to work as before if these settings are not specified in address.yaml. (OPSC-9398)
  • Added validation to os-metric/disk-space route. (OPSC-9928)
  • Enabled JVM heap dump by default for both opscenterd and the agent when there is an OutOfMemoryError. (OPSC-10861)
  • All memberOf attribute values are now evaluated during LDAP memberOf authentication. (OPSC-10893)
  • Included change details in audit log messages for updates to role permissions. (OPSC-10929)
  • Removed Clojure compiler warnings from agent startup. (OPSC-11068), (OPSC-11452)
  • Improved log messages when agents experience NFS read issues. (OPSC-11665)
  • Added validation of Content-Type header to agent API. (OPSC-10001)
  • No longer automatically install openjdk when directly installing OpsCenter from RPM or Deb packages. (OPSC-10260)
  • If OpsCenter authentication is enabled, users who do not have View Schema permission in their assigned role are not allowed to view schema data in the Data area of OpsCenter monitoring. OpsCenter presents an informational message that instructs users to contact their OpsCenter administrator for access. (OPSC-11319)
  • Fixed an issue which prevented some Solr operations from working correctly on multi-homed hosts. (OPSC-11437)
  • Fixed the /failover endpoint on the secondary OpsCenter instance. (OPSC-10720)
  • Fixed an issue which would cause opscenterd to mark an agent's http interface as down. (OPSC-10879)
  • Fixed a bug in agent lookup of datacenter name via JMX. This caused move token requests to fail during repairs. (OPSC-11788)
  • Fixed a potential SQL injection exploit in SQL authentication of OpsCenter (DatastaxEnterpriseAuth) in which an attacker could potentially gain access to the OpsCenter UI and its APIs using the password of any user that exists in the database. (OPSC-11991)
Monitoring
  • The schema viewer in the Data area of the OpsCenter Monitoring UI now displays materialized views, secondary indexes, and user-defined types used on a table. Users with permissions can view query statements on the new User-Defined Types, User-Defined Functions, and User-Defined Aggregates tabs. (OPSC-4760)
  • Hover tooltips that describe each column in the Agent status view have been added. (OPSC-10769)
  • Added route /v1/monitor to agent to retrieve self-monitoring data on cassandra, monitored and storage clusters, jmx, rollups, messaging, component state, etc. (OPSC-3492)
  • Added convenient UI access to critical logs from within the Node details dialog. The logs are a labs feature that must be enabled. See Viewing logs from node details. (OPSC-9442)
  • Added LiveScannedHistogram metric to track the number of cells scanned during a read. (OPSC-10786)
  • Allow overriding content of http callback alerts. (OPSC-11054)
  • Alert badges in the global dashboard show an alerts list when clicked. (OPSC-4625)
  • Added support for the SSTables Repaired metrics at the node and table levels for DSE 5.1. (OPSC-10495)
  • Added Start Time column to the slow query log table in the Performance Service. (OPSC-10537)
  • Fixed a bug where best practice rule for Compaction Strategy would not log a failure. (OPSC-10987)
Lifecycle Manager (LCM)
  • RLAC can now be enabled through LCM. (OPSC-10099)
  • LCM now allows jobs across clusters to run concurrently, but multiple jobs for the same cluster continue to run serially. (OPSC-8457)
  • LCM can no longer import clusters that have Hadoop enabled. Migrate to DSE Analytics prior to importing to LCM. (OPSC-10506)
  • LCM can no longer run jobs on clusters that have Hadoop enabled. (OPSC-10507)
  • The hive-site.xml file is now managed in the Spark section of the Configuration Profiles in LCM. (OPSC-10890)
  • Lifecycle Manager now validates cluster and datacenter names as ASCII strings instead of failing on non-ASCII characters during DSE installation. (OPSC-9276)
  • The DSE password now properly escapes the percentage (%) character. Users who escaped that character with the double %% workaround need to change their configuration back to a single %. (OPSC-9500)
Backup Service
  • OpsCenter now warns users that attempt to restore backups without setting an explicit throttle value for stream throughput. Applies to DSE clusters from versions 4.8.7 and later. (OPSC-10185)
  • The [cloud] group and its only property, accepted_certs, are no longer part of OpsCenter config. (OPSC-11114)
  • OpsCenter switched to the Amazon SDK for S3 functionality. (OPSC-10033), (OPSC-10036)
  • Added support for backup and restore by datacenter. (OPSC-6155)
  • Re-implemented bandwidth throttling for S3 operations to make them more efficient and accurate. (OPSC-10073)
  • Added support for cloning from a backup using Local FS. (OPSC-6135)
  • Improved bucket name validation to more closely match what is allowed by AWS. (OPSC-6183)
  • Added the ability to alert on backup failure to the Event log for failed backups. (OPSC-7635)
  • The config parameter backup_file_queue_max has been removed from address.yaml. (OPSC-8045)
  • The Commit Log Archiving Consistency Best Practice Rule has been added to ensure all nodes within a cluster have Commit Log Archiving enabled to prevent any data loss during a PIT restore. (OPSC-10299)
  • Added support for a Local FS backup location and additional S3 or local locations in the Point in Time restore dialog in the Backup Service. (OPSC-10665), (OPSC-10728)
  • Tables with no data in them are now captured in backup data and can have their schemas restored. (OPSC-6558)
  • Performance improvements with local and S3 destinations. (OPSC-11727)
  • Updated the commit log archiving template to prevent an bug where commit logs would be transferred incompletely to S3. Users with commit log archiving currently active need to disable then enable commit log archiving for this change to take effect. (OPSC-11903)
  • Fixed the Unrecognized config key warning in the agent logs. (OPSC-9609)
  • Fixed an issue where materialized views were offered as tables that could be restored directly. (OPSC-11917)
  • Fixed a bug where a backup to a destination would be marked as successful even though the schema.json failed to upload and OpsCenter would be unable to restore from it. (OPSC-10815)
Repair Service
  • Removed configuration settings from Repair Service that are no longer in use: ks_update_period, max_err_threshold, alert_on_repair_failure, repair_estimation_factor, incremental_range_repair. (OPSC-5895)
  • A new Status tab for the Repair Service conveys detailed information about subrange and incremental repairs. (OPSC-10020)
  • Removed the /<cluster ID>/services/repair/invalid_keyspaces API route since it is no longer used in the OpsCenter 6.1 Repair Service. (OPSC-11139)
  • The new Repair Service configuration option time_to_completion_target_percentage provides control over the speed with which repair jobs complete within the specified Time to completion parameter. See Adjusting or disabling the throttle for subrange repairs. (OPSC-2011)
  • Reworded log warning to use a less alarming phrase to describe an activation delay in the Repair Service. (OPSC-6453), (OPSC-8681)
  • Enhanced the Repair Service to ignore specific keyspaces and tables in addition to system keyspaces during a subrange repair. (OPSC-10458)
  • Excluded materialized views from incremental and subrange repairs. (OPSC-10955)
  • Clarified instructions for Time to completion and its relationship to gc_grace_seconds on the Repair Service settings page, plus provided links to relevant documentation. (OPSC-11454)
  • Removed the Repair Service progress bar from the Services page in lieu of a separate and much more detailed Repair Service status page. (OPSC-11560)
  • OpsCenter Services displays a Details link rather than a Configure link when services are already enabled. (OPSC-11661)
  • The target number of partitions per subrange can now be configured with the tokenranges_partitions configuration option. (OPSC-11801)
  • Added new Repair Service property tokenranges_http_timeout for setting a higher http timeout if necessary when retrieving tokenranges. (OPSC-11187)
  • Changed the system keyspaces excluded by the Repair Service to: dse_perf, system, system_distributed, system_schema, system_traces. (OPSC-11817)
  • Always now honor an API request to activate repair service. If a cluster is not yet in a stabilized state in which repairs can run, the Repair Service is activated in a paused state rather than raising an exception. (OPSC-11838)

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)