Home

v4.7.2.2 Release notes

Software version

Release Date: 22/Nov/2021

See 4.7.2.2 for download information.

Software upgrade support

  • 4.6.1.8 or earlier → 4.6.1.9 4.7.2.2

  • 4.6.1.9 4.7.2.2

  • 4.7.1.x 4.7.2.2

  • 4.7.2.0 4.7.2.2

  • 4.7.2.1 4.7.2.2

  • For Unravel TAR installations the following upgrade path is supported:

    • 4.6.1.x4.7.2.2

Sensor upgrade

  • Sensor upgrade is mandatory.

Certified platforms

The following platforms are tested and certified in this release:

  • Cloudera Distribution of Apache Hadoop (CDH)

  • Cloudera Data Platform (CDP)

  • Hortonworks Data Platform (HDP)

  • Amazon Elastic MapReduce (EMR)

  • Databricks (Azure Databricks and AWS Databricks)

  • Google Cloud Dataproc

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

Updates to Unravel's configuration properties

New features

  • None

Improvements and enhancements

  • Installation

    • Support upgrade path from 4616 TAR to 4722 TAR. (INSTALL-2071)

    • Removed prompt for admin user and password while enabling cloud migration. (INSTALL-2143, MIG-186)

  • Report

    • Support customizable ports for OnDemand reports. (REPORT-1477)

Unsupported

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

Bug fixes

  • Application

    • Impala: Queries are marked as processed even when a complete query profile tree is not available. (ASP-1276)

    • On the Job trends and Resources page, deselecting legends in the report do not apply filters for the tables. (CDI-385)

  • Databricks

    • Internal Server Error is displayed on Insights Overview > Cost section. (CDI-374)

    • Patch support for multiple LDAP servers. (CDI-372)

  • Installation

    • freeze-python-package does not show errors out of docker. (INSTALL-2078)

  • Migration

    • Cloud Mapping Per Host report: Host resource usages are shown as 0 for HDP. (MIG-182)

    • Workload Fit report fails with a misleading error message. (MIG-190)

  • UI

    • User domain-username provided for Userflow identity. (UIX-4331)

  • Upgrade

    • Hook up needed upgrade task for 4610_ms. (INSTALL-2075)

    • After an upgrade from 4.6.1.6 to 4.7.2.2 previously run Ondemand reports are not archived. (INSTALL-2149)

    • After an upgrade from 4.6.1.6 to 4.7.2.2, RM and sensor data for Spark and Tez are not visible. (INSTALL-2150)

    • After an upgrade from 4.6.1.6 to 4.7.2.2 Hive apps are not visible. (INSTALL-2148)

    • After an upgrade from 4.7.1.1 to 4.7.2.0 the hive_metastore check fails with an exception. (INSTALL-2153)

    • Upgrade from 4.5.5.5 RPM to 4.6.1.9 RPM to 4.7.2.2 TAR: The upgrade from 4.6.1.9 to 4.7.2.2 failed while initializing MySQL. (INSTALL-2154)

  • 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”: [
                    “pricing:GetProducts”,
                    “elasticmapreduce:ListClusters”,
                    “elasticmapreduce:DescribeCluster”,
                    “elasticmapreduce:ListInstanceFleets”,
                    “elasticmapreduce:ListInstanceGroups”,
                    “elasticmapreduce:ListBootstrapActions“,
                    “elasticmapreduce:ListInstances”,
                    “ec2:DescribeSpotPriceHistory”
                ],
                “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.

     kerberos:
          enabled: False
  • Cloud Mapping Per Host report: Failure to get instance list for certain cloud providers. (MIG-171)

    Workaround:

    1. Run dbcli.

      <Unravel installation directory>/unravel/manager run dbcli
      
    2. Make the following change in the database schema:

      ALTER TABLE celery_taskmeta CHANGE COLUMN result result MEDIUMBLOB;
  • 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)

  • In case you have configured a single cluster deployment for Unravel and the cluster name is not default, then the Datapage feature may not work properly.

    For this, you must explicitly set the following property after upgrading. (INSTALL_2151)

    <Unravel installation directory>/unravel/manager stop
    <Unravel installation directory>/unravel/manager config properties set hive.metastore.cluster.ids=<cluster-name>
    <Unravel installation directory>/unravel/manager apply
    <Unravel installation directory>/unravel/manager start
  • 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)

Support

For support issues, contact Unravel Support.