Skip to main content


v4.3.1.4 Release notes

Software version

Release Date: 06/18/2018 for

For details on downloading updates see Downloads.

Certified platforms
  • CDH: On-premise5.13 & 5.14 (including Spark 2.2.x) with Kerberos

  • HDP: On-premise HDP (up to v2.6) with Kerberos + spnego enabled.

  • MapR: 6.0.0 with MapR Expansion Packs 4.1.1

Unravel sensor upgrade
  • Optional

New features
  • Operations Page can now be disabled for Non-admin user. (CUSTOMER-74/UIX-516)

  • Support LDAP search-bind account for login. See Integrating LDAP Authentication. (PLATFORM-114)

Improvements and bug fixes
  • Fixed LDAP Integration issues during upgrade. (CUSTOMER-77)

  • SPARK Logs are now formatted for readability. (UIX-503)

  • The parameters listed in the Event Panel Recommendations are now sorted alphabetically. (UIX-369)

  • WorkFlow APM | Compare takes in consideration all application types. (PLATFORM-114)

Bug fixes
  • Tez App can now be retrieved on Cloudera. (CUSTOMER-102)

  • RBAC Bug fixes

  • Tag based RBAC now works. (CUSTOMER-75)

  • /usr/local/unravel/etc/ such file or directory) is no longer displayed unless tagging has been enabled/setup by setting: (Customer-25)

    • com.unraveldata.tagging.script.enabled=true



  • Reports | Data Insights UI Bug fixes

  • Details tab: Label Distribution Graph is now displayed and correctly populated. (DATAPAGE-20)

  • Overview: partition KPI's are accurately populated. (DATAPAGE-24)

  • Operations | Usage Details

  • Infrastructure: Business Tags drop down no longer duplicates tags. (UIX-519)

  • Impala:Tab is now paginated and applications are correctly displayed. (UIX-521/534)

  • Applications | Applications UI Fixes for IE11 Browser

  • Correctly displays all applications based on user query and the app count is correct. (UIX-581/585)

  • Corrected daemon confusion by correcting setting of CDH_CPATH. (INSTALL-35)

  • Corrected Too many CM Sockets in Close_Wait State. (IMPALA-31)

  • Username is now consistent across Impala query run and completion. (IMPALA-51)

Known issues
  • Tez

    • All Task Attempts ID duration is showing incorrect. (UIX-633)

    • Queue and cluster ID's are missing for Hive running on Tez engine. (UIX-718)

  • ActiveController count is shown as zero although active controller count for a cluster is one (1). (UKAFKA-9)

  • Operations | Dashboard: Inefficient Applications Tile list App count doesn't match app list. (UIX-681/678/514/401/223)

  • Operations | Usage Details: Auto refresh clears all the selected tags.

New configuration properties
  • None

Software upgrade support
  • Support for upgrade from 4.2.6 (4.2.6-1128) or 4.2.7 (4.2.7-1154)

  • Support for upgrade from 4.3.0.x to

  • Upgrading from 4.2.6 or 4.2.7 with this RPM causes a background process to run for about 15 minutes. During which data is migrated in the unravel_s_1 daemon. To see status of this migration, see /usr/local/unravel/install_bin/es_migrate_4.3.1.0_from42.out and /usr/local/unravel/logs/es_migrate_4.3.1.0_from42.log ; this migration can be re-run using/usr/local/unravel/install_bin/ in the background with nohup. When the migration finishes successfully, disk space can be saved by running /usr/local/unravel/install_bin/

  • An RPM upgrade triggers a temporary background process so changes can take effect. You can monitor it or wait for these with /usr/local/unravel/install_bin/ which prints DONE when it finishes. Tt takes anywhere from 2-15 minutes depending on your data size.

  • After upgrade:

  • Run /usr/local/unravel/install_bin/await_fixups.shand wait for it to finish. It can take up to 15 minutes. If shell is terminated, it can be run again at any time.

  • There should be 47 tables. Check the table count manually with and 'show tables;'. If fewer tables are present, run: sudo /usr/local/unravel/dbin/


Upgrade to 4.2.6 or later before upgrade to 4.3.x
Upgrading 4.2.x to 4.3.x, one-time potential must-do steps

When upgrading from 4.2.x to 4.3.x, you need to be cognizant of the run-as user for Unravel server daemons. Unravel Server 4.2.x and earlier runs daemons with 2 different local users (usually 'unravel' and 'hdfs' or 'mapr'). In 4.3.x, Unravel server simplifies this to run-as the single user 'unravel' by default. During an upgrade from 4.2.x to 4.3.x, all the daemons are converted over to user 'unravel'. Other changes that occur because of this:/srv/unravel/log_hdfs/* logs are moved to /usr/local/unravel/logs

  • /srv/unravel/log_hdfs/ directory is removed

  • /srv/unravel/tmp_hdfs/ is no longer needed, so it is removed (/srv/unravel/tmp/ is used instead)

  • env vars HDFS_KEYTAB_PATH and HDFS_KERBEROS_PRINCIPAL in /usr/local/unravel/etc/ no longer used

  • For Kerberos, com.unraveldata.kerberos.principal and com.unraveldata.kerberos.keytab.path are used instead.

After the first 4.3.x RPM upgrade, you MUST evaluate whether the must be run in order for Unravel Server to load logs via HDFS and to access kerberos-spnego protected REST endpoints. If MapReduce or Spark jobs stop loading after upgrade, that is a strong indication that you need to switch users. This script need only be run once. See Run Unravel Daemons with Custom User for more details. Subsequent upgrades 4.3.x to 4.3.y will not need to run script.

Upgrade process

An RPM upgrade will trigger a temporary background process so changes can take effect. You can monitor or wait for these with /usr/local/unravel/install_bin/ which prints "Done" when it finishes. The script waits and prints ps of the background process. It might take 2-5 min. depending on your data size.

The background fixups will produce log file output in:

  • /tmp/unravel_post_upgrade_fixups.*.out

  • /tmp/unravel_schema.*.out

  • /usr/local/unravel/logs/unravel_schema.log

  • /usr/local/unravel/logs/es_migrate_4.3.1.0_from42.*

  • /usr/local/unravel/logs/unravel_esm.log

For further support, contact Unravel Support.