Home

v4.3.1.0 Release notes

Software version

Release Date: 04/13/2018

For details on downloading updates see here.

Certified platforms

  • CDH: On-premise CDH (up to v5.13) with Kerberos enabled.

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

  • MapR: Testing is in progress.

  • EMR: Testing is in progress.

  • Qubole: Testing is in progress.

Unravel sensor upgrade

  • Optional

    • See Improvements and Bug Fixes for list of sensor fixes/upgrades.

New features

  • Significant improvement in speed to UI based on new technology stack (Angular + Node.js)

  • Merged Operation > Reports & Data tab into new Reports Tab to locate all reports together.

  • Added ability to chose the what columns to display in Applications tables.

  • Added ability to filter apps and resource usage graphs based on tags, e.g., user groups, projects, department.

  • Roles has been expanded to allow the Admin to limit the Endusers to the Applications tab. Admin can further restrict their access to applications based upon tags, i.e., projects, departments. See Role Based Access.

  • Running Unravel daemons as a single user see Run Unravel Daemons with Custom User. (UNRAVEL-2449)

  • Added support for Application Master job counters in Auto Action v2 rules. (UNRAVEL-2621)

  • Added container level aggregation in Auto Action v2. (UNRAVEL-2612)

  • Added support for "sustained" violation detection in Auto Action v2. (UNRAVEL-1084)

  • Link to Unravel Documentation on title bar.

Improvements and bug fixes
Improvements

  • Improved Auto Action email / Slack message subject, removed misleading “only for <state>” phrase and make message more readable. (UNRAVEL-3021)

  • All emails and Slack messages sent from Unravel server now include the organization information as set in Unravel server settings. (UNRAVEL-2509)

  • Split "kill_app" and "move_to_queue" action in conditional and non-conditional. (UNRAVEL-2110)

Bug fixes

  • Fixed very rare but possible ConcurrentModificationException in Auto Action internal metric stream. (UNRAVEL-3173)

  • Fixed aggregates metrics tracking bug caused by aggregator sharing in Auto Action v2 backend. (UNRAVEL-2903)

  • Fixed exception when trying to read Auto Action v1 rule. (UNRAVEL-2891)

  • Fixed “aggregate.Aggregator: found and removed orphan aggregate” error in Auto Action v2 backend. (UNRAVEL-2467)

  • Fixed a bug that caused non-Oozie workflows metrics to be ignored by Auto Action v2 backend. (UNRAVEL-2515)

Sensors

  • Allow slowing down metrics collection in sensor agent. (UNRAVEL-2858)

  • Properly close connections when using HttpUrlConnection. (UNRAVEL-2749)

  • Pre-resolve and cache IP address of Unravel server. (UNRAVEL-2015)

  • Sensor support for bringing in job annotations live. (UNRAVEL-2977)

  • Backend support for streaming applications. Changes have been implemented to the StreamingProbe. (UNRAVEL-2819)

  • Probes initialization when profiling apps in trace and debug modes. (UNRAVEL-3182)

Known issues

  • Kafka Monitoring

  • Tez support

Warning

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

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/unravel.ext.sh 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 switch_to_user.sh 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 switch_to_user.sh script.

For further support, contact Unravel Support.

In this section: