Skip to main content

Home

v4.7.9.1 Release notes

Software version

Release date: 03/July/2023

See 4.7.9.1 for download information.

Software upgrade support

The following upgrade paths are supported:

  • 4.7.x.x → 4.7.9.1

  • 4.7.5.0 Hot fix → 4.7.9.1

  • 4.6.1.9 → 4.7.9.1

  • 4.6.1.8 or earlier → 4.6.1.9 → 4.7.9.1

For instructions to upgrade to Unravel v4.6.1.9, see Upgrading Unravel server.

For instructions to upgrade to Unravel v4.7.9.x, see Upgrading Unravel.

For fresh installations, see Installing Unravel.

Sensor upgrade

  • Sensor upgrade is mandatory for on-prem platforms when you upgrade to Unravel 4.7.9.1. Refer to Upgrading Sensors

Certified platforms

The following platforms are tested and certified in this release:

On-premise platforms

  • Cloudera Distribution of Apache Hadoop (CDH)

  • Cloudera Data Platform (CDP)

  • Hortonworks Data Platform (HDP)

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

Updates to Unravel's configuration properties

Updates to upgrading Unravel to v4.7.9.1

Obtain License file

An existing license for any previous version does not work with the newer version of Unravel. Therefore, before upgrading Unravel, you must obtain a license file from Unravel Customer Support. For information about setting the license, see Upgrading Unravel from version 4.7.x to 4.7.9.x section in Upgrading Unravel.

Re-configure the custom ports after upgrading from versions before v4.6.1.9

In the case of an Unravel version before v4.6.1.9, you have a customized UI port, for example, 4000, then after the upgrade, this port reverts to the default 3000. Hence, after you upgrade to 4.7.9.1, you must reconfigure the custom port.

  1. Stop Unravel.

    <Unravel installation directory>/unravel/manager stop

  2. Display the list of ports and keys.

    <Unravel installation directory>/unravel/manager config ports show

  3. Set the port using the following command with the port and port key.

    <Unravel installation directory>/unravel/manager config ports set <port key> <port>

    For example, if you run the following command, NGUI listens on port 1234.

    <Unravel installation directory>/unravel/manager config ports set /hosts/host_main/instances/ngui_1/config/network/port 1234

    Note

    • Run manager config ports unset <port key> command to return the ports to their default values. 

      <Unravel installation directory>/unravel/manager config ports unset /hosts/host_main/instances/appstore_1/config/flask/port

  4. Apply the changes.

    <Unravel installation directory>/unravel/manager config apply

  5. Start Unravel.

    <Unravel installation directory>/unravel/manager start
Unset/set properties on the HDP to CDP migrated cluster

After you have migrated from an Hortonworks Data Platform (HDP) to a Cloudera Data Platform (CDP) cluster, there are some properties you must unset and new properties that you must set on an edge node of the migrated cluster.

Single-cluster (HDP to CDP migration)

  1. On the edge node, set the following property: 

    <Unravel installation directory>/unravel/manager config properties set com.unraveldata.cluster.type CDP

    In case HBase was configured earlier, then set the following property: 

    <Unravel installation directory>/unravel/manager config properties set com.unraveldata.hbase.source.type=CDP

  2. Unset the following properties: 

    <Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.url
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.username
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.password
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.yarn.timeline-service.webapp.address
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.yarn.timeline-service.port

  3. Run manager config auto command to pull in all the Hadoop configurations automatically. You will be prompted to provide the location and credentials for the CDP Cloudera manager URL.

    <Unravel installation directory>/unravel/manager config auto

    If there are more than one clusters that are handled by the CDP Cloudera manager, then you are prompted to enable the cluster that you want to monitor. Run the following command to enable a cluster:

    <Unravel installation directory>/unravel/manager config cluster enable <CLUSTER KEY>

    Example: /opt/unravel/manager config cluster enable cluster1

  4. Apply the changes.

    <Unravel installation directory>/unravel/manager config apply

  5. Start Unravel.

    <Unravel installation directory>/unravel/manager start

  6. Ensure to make the following changes in the Cloudera manager:

    • HDP/CDH has hive hooks under HIVE service, but for CDP, it is under HIVE_ON_TEZ. Hence, you must update the properties accordingly.

    • Update CDP Version for sensor parcel in Parcel Repository & Network from Cloudera Manager to https://xxx.unraveldata.com:3000/parcels/cdh7.1/

    • Check for new parcels and distribute them.

Multi-cluster (HDP to CDP migration)

In case of a multi-cluster environment, do the following:

  1. Log in to the core node as an Unravel user.

  2. Unset the following properties on the core node:

    <Unravel installation directory>/unravel/manager config properties unset com.unraveldata.cluster.type
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.url
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.username
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.password
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.<EDGE KEY>.url
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.<EDGE KEY>.username
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.<EDGE KEY>.password
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.ambari.manager.list

    Tip

    Run the following commands to obtain the <EDGE KEY>.

    <unravel_installation_directory>/unravel/config edge show

    Run the following commands to obtain the <CLUSTER KEY>.

    <unravel_installation_directory>/unravel/manager support show cluster_access_id/unravel/config edge show

    Note

    For a multi-cluster environment, if your cluster name changes after the migration from HDP to CDP, you must unset the following properties on the core node:

    <Unravel installation directory>/unravel/manager config properties unset javax.jdo.option.<EDGE KEY>_<CLUSTER KEY>_HIVE.ConnectionURL
<Unravel installation directory>/unravel/manager config properties unset javax.jdo.option.<EDGE KEY>_<CLUSTER KEY>_HIVE.ConnectionDriverName
<Unravel installation directory>/unravel/manager config properties unset javax.jdo.option.<EDGE KEY>_<CLUSTER KEY>_HIVE.ConnectionUserName
<Unravel installation directory>/unravel/manager config properties unset javax.jdo.option.<EDGE KEY>_<CLUSTER KEY>_HIVE.ConnectionPassword
<Unravel installation directory>/unravel/manager config properties unset hive.metastore.<EDGE KEY>_<CLUSTER KEY>_HIVE.cluster.ids
<Unravel installation directory>/unravel/manager config properties unset hive.metastore.<EDGE KEY>_<CLUSTER KEY>_HIVE.cluster.ids
<Unravel installation directory>/unravel/manager config properties unset com.unraveldata.hive.metastore.list

  3. Run the following command:

    <Unravel installation directory>/unravel/manager config edge auto <EDGE KEY>

  4. Apply the changes.

    <Unravel installation directory>/unravel/manager config apply

  5. Start Unravel.

    <Unravel installation directory>/unravel/manager start

New features

No new features have been added in this release of Unravel.

Improvements and enhancements

  • Performance improvements

    • Optimized configuration handling

    • Improvements in concurrent statistics updates

  • Data page scaling

    • Data page performs efficiently with extensive scaling. Scale performance tested using Hive metastore with 2000000 tables and 17000000 partitions.

    • Configuration properties introduced to modify the batch size and set the polling limits for table metadata and partitions metadata.

  • Impala and YARN cluster identification from cluster ID

    The cluster type is included with the cluster ID, which helps in identifying the Impala and YARN clusters. (PLATFORM-3003)

  • FSImage

    • A new configuration property unravel.python.fsimage.java.home has been added to set JAVA home for FSImage processing. ( SUPPORT-2015)

  • UI enhancements

    Implemented consistent usage of UI elements such as cluster ID, tooltips, download CSV option, and so on. (PLATFOM-3003)

  • Other enhancements

    • A new configuration property com.unraveldata.metrics.factor has been added to skip metrics updates for individual applications using a configured metrics factor as done on the sensor side. Refer to 4791 Updates to Unravel properties for more details. ( PIPELINE-1868)

Bug fixes

  • Installation

    • After changing the default value of the host_monitor port, the Monitoring page (Manage > Monitoring) does not load. (INSTALL-3193)

  • Hive on Spark

    For Hive on Spark, the Stage timeline view on the Hive page is not showing any data. (UIX-6149)

  • UI

    On the Clusters > Workload page, after modifying the Display items per page setting from 10 to 50, selecting any insight (such as Policy Violation) redirects to the default setting of 10 items per page. (UIX-6033).

Unsupported

App Store

  • Appstore does not support PostgreSQL over SSL.

Billing

  • Unravel does not support Billing for on-prem platforms.

Healthcheck

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

Platforms
MapR

The following features are not supported for MapR:

  • Impala applications

  • Kerberos

  • The following features are not supported on the Data page:

    • Forecasting

    • Small Files Report

    • File Reports

  • The following reports are not supported on MapR:

    • File Reports

    • Small Files Report

    • Capacity Forecasting

    • Cloud Migration reports

  • AutoAction is not supported for Impala applications.

  • Billing

  • Insights Overview

Migration planning

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

Multi-cluster deployment

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

  • Automatic FSImage processing is not supported for multi-cluster environments.

Pipeline

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

Known issues

Applications

  • On the Table Details page under the Applications tab, inaccurate data is displayed for a table. This issue occurs if a table is deleted and recreated multiple times and applications executed to access the table before the next cycle of the table worker. (PG-156)

AutoActions

  • AutoActions stop responding due to an invalid or unsupported HTTP URL or webhook. (AA-575)

App Store

  • App Store tasks fail to start with SSL enabled on MySQL database. (APP-614)

    Workaround

    To resolve this issue, do the following:

    1. Stop Unravel.

      <Unravel installation directory>/unravel/manager stop

    2. Use an editor to open <Installation_directory>/unravel/data/conf/unravel.yaml file.

    3. In the unravel.yaml file, under the database > advanced > python_flags block, enter the path to the trusted certificates. For example, if Unravel is installed at /opt/unravel, you must edit the unravel.yaml file as follows:

      unravel:
...snip...
  database:
...snip...
    advanced:
      python_flags:
        ssl_ca: /opt/unravel/data/certificates/trusted_certs.pem

    4. Use the manager utility to upload the certificates.

      <Unravel installation directory>/manager config tls trust add --pem /path/to/certificate

      For example: /opt/unravel/manager config tls trust add --pem /path/to/certificate

    5. Enable the Truststore.

      <Unravel installation directory>/manager config tls trust enable

    6. Apply the changes and restart Unravel. 

      <Unravel installation directory>/unravel/manager config apply --restart
Data page

  • If tables are created with the same name and are accessed, deleted, and re-created, and if those tables are re-accessed, then their query and app count do not match. (DATAPAGE-502)

  • The query to fetch tableDailyKPIs is getting timed out in case of a huge table partition (27 million). (DATAPAGE-740)

  • For Hive metastore 3.1.0 or earlier versions, the creation time of partitions is not captured if a partition is created dynamically.  Therefore, the Last Day KPI for the partition section is not shown in Unravel. (DATAPAGE-473)

  • On the Data page, size data is missing for certain tables in databases, although the partition size is correctly displayed in the Partition Detail section. (DATAPAGE-695)

Installation
    Insights Overview

    • 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 differ. (UIX-4176)

    Kerberos

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

       kerberos:
      enabled: False
    Migration

    • WorkloadFit report

      • A large number of tags can cause the Workload Fit report to fail. (PG-265, CUSTOMER-2084)

      • WorkloadFit report > Heatmap: The job count has data, but Vcore and memory are empty. (MIG-262)

    • Inconsistency between the regions displayed on the Unravel user interface and the ones included in AWS EMR. (MIG-280, MIG-281)

    • The Cloud Mapping Per Host migration report fails for some regions. (MIG-303)

    Reports

    • Cluster discovery

      • The On-prem Cluster Identity might 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)

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

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

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

    Tez

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

    Upgrade

    • After upgrading to v4.7.1.0, Notebooks do not work. You can configure them separately. (REPORT-1895)

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

    UI

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

    • When you click the hive query, which was executed as part of the Hive on Spark application, a blank page is shown. (UIX-6037)

    • On the Clusters > Resources page, in the Group By drop-down list, the Application Type, User, and Queue options are duplicated for the YARN/IMPALA resource job type. The issue occurs if identical user-defined tags are used. (UIX-5898)

    Workflow

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

    Support

    For support issues, contact Unravel Support.

    In this section: