Skip to main content


v4.6.1.5 Release notes

Software version

Release Date: 10/17/2020

See v4.6.1.5 for download information

Software upgrade support

In v4.6.1.5, the following paths are supported for Tarball and RPM upgrades:

Tarball supported upgrade path

RPM supported upgrade path to to to to to to to to to

Sensor upgrade
  • A sensor upgrade is mandatory.

Certified platforms

Review your platform's compatibility matrix before you upgrade or install.

Updates to Unravel's configuration properties
New features
  • None

Improvements and enhancements
  • None

  • Cloud platforms (Databricks, Azure HDInsight, Amazon EMR)

  • On-premise platforms - (MapR)

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

    • US DoD East

    • US DoD Central

    • Germany Central (Sovereign)

    • Germany Northeast (Sovereign)

Upgrade instructions

This section provides instructions to upgrade to Unravel v4.6.1.5.

RPM upgrade

For Unravel RPM upgrade, refer to Upgrading Unravel server

Tarball upgrade

This section provides instructions for the Unravel Tarball upgrade.

The following assumptions are made in the upgrade instructions:

  • Unravel is installed to /unravel-ro. You can verify the correct directory name by looking for the software directory in that location. For example: /unravel-ro/software.

  • Unravel is configured with /unravel-rw as the writable location. You can verify the correct directory name by looking for a data directory. For example: /unravel-rw/data.

To install Unravel from a tar file, do the following:

  1. Change directories to /unravel-ro.

  2. Download Unravel.

    curl -v -o unravel- -u username:password
  3. Untar unravel-

    tar zxf unravel- -C /unravel-ro 
  4. Stop Unravel.

    /unravel-rw/service/ stop
  5. Run the setup script.

    /unravel-ro/unravel/versions/ --migrate-ms /unravel-rw/data
  6. (Optional) Refresh the cluster configuration.

    /unravel-rw/manager config auto
  7. Start unravel.

    /unravel-rw/manager start
  8. Check the status.

    /unravel-rw/manager report
Bug fixes
  • Spark

    • SW daemons crashing while storing SQL data processed from the event log. (USPARK-775)

    • Issues in processing data for applications that use multiple attempts. (USPARK-738)

    • The status bar in the navigation table of the Applications detail page shows negative and incorrect values. (USPARK-782)

    • Performance degradation observed in the before and after runs of the Spark Insight application. (USPARK-731, USPARK-780)

    • The latest Spark events are marked as stale if the Spark app has multiple attempts. (USPARK-774)

  • Insights

    • Unable to access the WorkFlow from the Application page. (PLATFORM-2463, PLATFORM-2813)

  • Platform

    • Executor core recommendation is not generated appropriately in case of a large number of parallel stage buckets. (INSIGHTS-56)

  • UI

    • Improper alignment of the back button in the Timings tab is fixed. (UIX-3482)

    • The Running Yarn Application count shown on the Operation page is not matching with actual running applications. (UIX-3479)

    • Loading the Session diff analysis page takes a longer time. (UIX-2595)

  • Reports

    • Capacity Forecasting cannot be run because OnDemand is not able to retrieve hdfs-site.xml from the Cloudera Manager APIs. (CUSTOMER-1436)

    • Issues in processing data for applications that use multiple attempts. (USPARK-738)

    • Small Files report now shows 10000 directories. (CUSTOMER-1506)

    • File Reports: The image process for fsimage fails with legacy installer. (REPORTS-1665)

  • Sessions

    • Sessions generate the same recommendations for consecutive runs. (SESS-335)

    • The Session apply feature does not function in a kerberized environment. (SESS-329)

  • EMR: Hive metrics are not published in the RUNNING state. (HIVE-135)

  • INSERT statements are not included in the App count on HDI. (DATAPAGE-256)

  • The accessed partition does not support Hive on Tez etc. It only supports Hive on MR. (DATAPAGE-250)

  • Datapage does not load the total table and partition size KPI's (DATAPAGE-379)

  • After Upgrading from v4.5.x to v4.6.1.5, the live resource metric data is not seen in the UI until the MA daemon is restarted. (INSTALL-802)

  • gc load metric sensor for MR application will not load on EMR.

  • Load container logs for oozie launcher job on HDP 3.1 (PLATFORM-2822)

  • Spark applications that run in local mode are shown with zero resources. (PLATFORM-2809)

  • Intermittent issue in fetching the Btrace data for MR applications. (PLATFORM-2807)

  • Killed MR apps do not display RM diagnostics. (PLATFORM-2815)

  • Certain users and queues are missing in the Cluster Compare report. (REPORT-1342)

  • In the Cluster Compare report, the trends of the same values are highlighted instead of trends with different values. (REPORT-1479)

  • Auto Tune: Automatic comparison of the first and last run fails. (SESS-333)

  • Unable to create session when space is used in the session name. (SESS-332)

  • There is a lag seen while streaming Spark SQL applications. (PLATFORM-2764)

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

  • Partition size 0 is shown in the insight message on the timings tab. (USPARK-647)

  • The number of Apps is incorrect. (PLATFORM-2403)

  • Spark apps running in Oozie workflow is not visible under Oozie workflow in Unravel UI. (PLATFORM-2746)

  • For streaming applications, the global search with application ID does not work. (UIX-3312)

For support issues, contact Unravel Support