Skip to main content


v4.7.0.1 Release notes

Software version

Release Date: 01/Jun/2021

See v4.7.0.1 for download information.

Software upgrade support

The following upgrade paths are supported:

Tarball supported upgrade path

RPM supported upgrade path to to to to to to

Sensor upgrade

  • Sensor upgrade is mandatory if you are upgrading from Unravel versions and

Certified platforms

The following platform is tested and certified in this release:

  • Hortonworks Data Platform (HDP)

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

Updates to Unravel's configuration properties

  • No updates to user-facing properties.

New features

  • Platforms

    Unravel version 4.7x is supported for Hortonworks Data Platform (HDP) for a single cluster environment as well as a multi-cluster environment.

  • FSImage configuration with Unravel Manager service

    The FSImage can be easily configured using the Unravel Manager service.

  • Unravel upgrade with Unravel Manager service

    Using the Unravel Manager service, you can upgrade to the Unravel 4.7x version. The following upgrade paths are supported in v4.7.0.1 for both RPM and Tar installation:

    • v4.6.2.1 to v4.7.0.1

    • v4.6.2.0 to v4.7.0.1

Improvements and enhancements

  • None


  • Billing is not supported on EMR and on-prem platforms.

  • 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, only a single cluster can be configured 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.

Bug fixes

  • Data page

    • Size information is not captured in daily KPIs when tables are dropped and recreated. (DATAPAGE-464)

  • Databricks

    • PartitioneNotPruned is not generated for Databricks. (INSIGHTS-122)

  • Security

    • CheckLicenseExpired fails when TLS is enabled. (INSTALL-1549)

  • Kafka

    • Total Fetch Requests per Sec metric in Kafka monitor displays much lesser value than the value displayed on Cloudera Manager. (CUSTOMER-1687)

  • Duplicate apps with the same cluster UID entry are found in Elastic Storage. (ASP-1044)

  • com.unraveldata.clusteraccess.hdfsconnector.api.HdfsConnectorException error is shown in the yarn_jc_sensor.log file. (PLATFORM-2956)

  • Kerberos can be only disabled manually from the unravel.yaml file.

          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)

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

  • Spark Analyse session fails in the absence of event logs for the applications present in the session. (SESS-366)

  • Session creation from the Hive application page is not supported. (UIX-3577)

    Workaround: Use the Sessions listing page to create a hive session.

  • The session should be sorted by create date instead of session names. (SESS-368)

  • Status of Application is seen as UNKNOWN in session details when the application has multiple attempts. (SESS-369)

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

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

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

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