Skip to main content


v4.7.2.1 Release notes

Software version

Release Date: 22/Oct/2021

See for download information.

Software upgrade support

Only fresh installations are supported.

Sensor upgrade

  • Sensor upgrade is mandatory.

Certified platforms

The following platform is tested and certified in this release:

  • Cloudera Data Platform (CDP) 7.1.7 version

Review your platform's compatibility matrix before you install Unravel.

Updates to Unravel's configuration properties

New features

  • None

Improvements and enhancements

  • None


  • Unravel does not support Billing on EMR and on-prem platforms.

  • On the Data page, File Reports, Small File reports, and file size information are not supported for EMR and Databricks clusters.

  • Impala jobs are not supported on the HDP platform.

  • Monitoring the expiration of the SSL Certificates and Kerberos principals in Unravel multi-cluster deployments.

  • Migration Planning is not supported for the following regions for Azure Data Lake:

    • Germany Central (Sovereign)

    • Germany Northeast (Sovereign)

  • Forecasting and Migration: In a multi-cluster environment, you can configure only a single cluster at a time; hence reports are generated only for that single cluster.

  • Unravel does not support multi-cluster management of combined on-prem and cloud clusters.

  • Unravel does not support apps belonging to the same pipeline in a multi-cluster environment but is sourced from different clusters. A pipeline can only contain apps that belong to the same cluster.

  • Reports are not supported on Databricks and EMR.

In Jobs > Sessions, the feature of applying recommendations and then running the newly configured app is not supported.

  • Pig and Cascading applications are not supported.

  • Upgrade to Unravel version from Unravel version TAR installation is not supported.

Bug fixes

  • Applications

    • Global search functionality is broken. (ASP-1251)

    • Queue name not being displayed for majority of the applications on Unravel UI. (ASP-1248)

    • All DAGs are not visible on the UI for Tez applications. (ASP-1260)

    • Data not loading for Hive-on-Tez queries. (ASP-1263)

    • On the Jobs page, the duration shown for some of the apps is erroneous. (ASP-1249)

    • Multiple issues fixed for application listing page. (ASP-1251, ASP-1248, ASP-1044)

  • Databricks

    • Unable to sort jobs/runs on the Cloud Clusters > Inefficient tab by cost or duration. (SUPPORT-851)

    • UI login takes about 2 min for loading cluster names. (SUPPORT-839)

    • In Jobs>Runs tab and Cloud Clusters tab, when you change the selected time interval to another interval, and you are on a page that is not included in the new interval, the tab does not display any data. (UIX-4205)

  • Installation

    • Provide a workaround for ondemand not using the TrustStore. (INSTALL-2030)

    • Installer: The start script templates should wait for pidfile creation. (INSTALL-1965)

    • Even after successfully configuring TLS, the ngui_http_is_alive check fails with Can't connect to Unravel UI error during TLS verification. (INSTALL-2034)

    • Incorrect values are shown during sensor verification after successful completion of additional instrumentation. (INSTALL-2033)

    • Workaround provided for python script not using configured TrustStore. (INSTALL-2033)

  • Insights

    • Empty recommendations are shown. (INSIGHTS-211)

    • Recommendations for Spark applications appear incorrect. (INSIGHTS-209)

    • All the counts for the DAGs are shown as 0. (INSIGHTS-208)

    • A negative value is shown for recommendations. (PG-182)

    • Data Skew event is not generated for applications with data skewness. (INSIGHTS-205)

    • Disabling SqlLargeResultEvent as it shows a wrong number of output rows. (INSIGHTS-213)

    • Incorrect recommendation is shown under Current Value for config event after run. (INSIGHTS-214)

  • Migration

    • Workload fit report: Cost is not displayed for Azure (Australia Central). (MIG-178)

    • Add CDP 7.1.7 service definitions for migration reports. (MIG-177)

    • For some Migration reports, when exceptions occur, the error messages are not displayed. (MIG-172)

  • UI

    • Inefficient apps page displays incomplete details when navigated from Insights Overview page. (UIX-4264)

    • Custom Table Sorting for non-numeric fields is broken. (UIX-4263)

    • On the Audit page, sorting does not work for all the columns. (CDI-358, UIX-4263)

    • Provide accuracy to details on Vertex timeline for Tez. (UIX-4265)

    • Missing the Tables listing on Tez DAG page. (UIX-4269)

    • Clusters > Workload: Impala applications are not listed in the table. (UIX-4270)

    • Tez logs are misprinted on the UI. (UIX-4271)1

    • Hide Bytes, Records, and Attempts in Hive application details table. (UIX-4277)

    • Jobs > Applications > All: When user clicks Copy App Name/ID the entire app disappears and reappears after 2-3secs. (UIX-4274)

    • Overview > Clusters: Nodes/cores/memory date becomes 0 and requires a page refresh to update the values. (UIX-4276)

    • Resource Usage tooltip truncates content on container edge. ((UIX-4279)

    • Clusters > Workload: Impala applications count shows 0 in the report. (UIX-4280)

    • Vertex Timeline color scheme changes after refresh. (UIX-4266)

  • Event logs and YARN logs are not loaded for some applications in Google Dataproc clusters. (PG-170)

  • In the Spark apps details page, under the Resources tab, the label denoting attempts in resource graphs appears distorted. (PG-169)

  • Create time of partitions does not get captured in hive metastore if the partition is created dynamically. This limits Unravel to show Last Day KPIs for the partition section.

  • Wrong data displayed for Number of Partitions Created KPI/trend graph under Partitions KPIs - Last Day section in theData page. (DATAPAGE-473)

  • Exception: Problem when retrieving bootstrap actions for cluster is seen in the aws_worker daemon logs.

    Workaround: While creating AWS account for EMR Chargeback/Insights overview feature, you must include an additional entry in the Policy JSON file for "elasticmapreduce:ListBootstrapActions", as follows:

        “Version”: “2012-10-17",
        “Statement”: [
                “Effect”: “Allow”,
                “Action”: [
                “Resource”: “*”

    Even though the AWS account was already created without this entry (elasticmapreduce:ListBootstrapActions), you can always include this policy later.

  • Unravel node fails to send email notifications. (INSTALL-1694)

  • The Insights Overview tab uses UTC as the timezone while other pages use local time. Hence, the date and time shown on the Insights Overview tab and the other pages after redirection can be different. (UIX-4176)

  • Kerberos can only be disabled manually from the unravel.yamlfile.

          enabled: False
  • Cluster discovery

    • If the metric retrieval for a host fails, then the CPU and memory capacity/usage graphs and heatmaps are not displayed.

      This happens on a CDH cluster when the Cloudera Manager agent of a host does not send any heartbeats to the Cloudera Manager server. Such a host is shown as Bad Health in Cloudera Manager. (REPORT-1706)

      Workaround: Ensure that the Cloudera Manager agent sends heartbeats to the Cloudera Manager on all hosts and that none of the hosts are shown as Bad Health.

    • The On-prem Cluster Identity may show an incorrect Spark version on CDH. The report may incorrectly show Spark 1 when Spark 2 is installed on the CDH cluster. (REPORT-1702)

  • When using PostgreSQL, the % sign is duplicated and displayed in the Workload Fit report > Map to single cluster tab. (MIG-42)

  • Cloud Mapping Per Host  report scheduled in v4.6.1.x will not work in v4.7.1.0. Users must schedule a new report. (REPORT-1886)

  • The TopX report email contains a link to the Unravel TopX report instead of showing the report content in the email as in the old reports.

  • Queue analysis: The log file name (unravel_us_1.log) displayed in the error message is incorrect. The correct name of the log file is unravel_sensor.log. (REPORT-1663)

  • The sensor setup script fails with unrecognized arguments. (INSTALL-1667)

  • There is a lag seen for SQL Streaming applications. (PLATFORM-2764)

  • If the customer uses an active directory for Kerberos and the samAccountName and principal do not match, this can cause errors when accessing HDFS. (DOC-755)

  • In AAD login mode when external logout happens, the user still has access to his current logged-in UI. (UI-4125)

  • For PySpark applications, the processCPUTime and the processCPULoad are not captured properly. (ASP-626)

  • SQL events generator generates SQL Like clause event if the query contains like pattern even in the literals. (TEZLLAP-349)

  • Notebooks will not work after upgrading to v4.7.1.0. You can configure them separately. (REPORT-1895)

  • After you upgrade from v4.6.x to v4.7.1.0, the Tez application details page does not initially show DAG data. The DAG data is visible only after you refresh the page. (ASP-1126)

  • On the Manage page, the DB Stats are not displayed for untracked clusters. (UIX-4171)

  • The new user interface (UI) can be accessed only from Chrome.

  • In the App summary page for Impala, the Query> Operator view is visible after scrolling down. (UIX-3536).

  • Jobs getting falsely labeled as a Tez App for Oozie Sqoop and Shell actions. (PLATFORM-2403)


For support issues, contact Unravel Support.