Humio Server 1.9.0 Preview (2020-03-12)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
ValueJAR Checksum

UI for Role Based Access Control (RBAC), Health Check API, Kafka Version Update, Vega Charts

Bug Fixes

  • Summary

    • Queries involving join can now be with 'used export to file' and the /query HTTP endpoint.

    • New caseSensitive option added to the parseTimestamp query function.

    • Updated Kafka and Zookeeper Docker images to use Kafka 2.4. Updating to Kafka 2.4 should be straightforward using Humio's Kafka/Zookeeper Docker images. Zookeeper image will handle migration. Stop all Kafka nodes. Stop all Zookeeper nodes. Start all Zookeeper nodes on the new version. Start all Kafka nodes on the new version. Before updating Kafka/Zookeeper, we recommend backing up the Zookeeper data directory. Then, add the Zookeeper properties described below. If you are deploying Kafka/Zookeeper using other tools, for example Ansible scripts, be aware there is a migration involved in updating Zookeeper.

    • When updating Kafka/Zookeeper we recommend setting these Zookeeper properties

      • Do not start the new admin server. Default port 8080 conflicts with Humio port.admin.enableServer=false

      • purge old snapshot files autopurge.purgeInterval=1

      • Allow 4 letter commands. Used by Humio to get info about the Zookeeper cluster 4lw.commands.whitelist=*

    • Improved (reduced) memory consumption for live groupby, and for groupby involving many distinct keys.

    • Be aware that updating Kafka also requires you to update Zookeeper to 3.5.6. There is a migration involved in updating Zookeeper. See Zookeeper's migration FAQ here. Use the migration approach using an empty snapshot. The other proposed solution can loose data.

    • Updated Humio to use Kafka 2.4. Humio can still use versions of Kafka down through 1.1.

    • New selectLast function, which is like select but aggregate.