Humio Server 1.14.0 Stable (2020-08-26)

VersionTypeRelease DateEnd of SupportUpgrades FromData MigrationConfig. Changes
1.14.0Stable2020-08-262021-08-261.12.0NoNo
JAR ChecksumValue
MD5d0ede2c5d1075119507701bff7a04b29
SHA1b4fc3f50fabe0abdea5db2a2b502c0b2b0b71aa7
SHA256e9ddafa574576eb890cf22d241e0307caf613cc5b1bd9fdc84e50e975a40d67b
SHA51216506530541f87579660b630265171c137b8de787b5c5d11b145fc1d18ff04038514b91469b040212dbd27bddc2cee4cb5cca0054f547917624137fedb23ba20

Free Text Search, Load Balancing of Queries and TLS Support. This release promotes the latest 1.13 release from preview to stable. To see more details, go through the individual 1.13.x release notes (links in the changelog).

Bug Fixes

  • Configuration

    • Other changes: (see 1.13.1 release notes)

    • Other changes: (see 1.13.5 release notes)

    • Major changes: (see 1.13.0 release notes)

    • Handling of digest in the case where a node has been offline for a long time has been improved. As an example, running a Humio cluster with a replication factor of 2 and having one node go offline for a long time would leave some ingested data to only reside on one Humio node (and on the ingest queue in Kafka). But this data would not be regarded as properly replicated until the second node returned. If the only node that was left handling a digest partition did a failover, Humio would end up going far back on the Kafka ingest queue to reread data. This has been changed. Now another node from the set of digest nodes will take over if a node goes offline, to keep the replication factor as desired. This means that other hosts, than those specified for a given digest partition on the cluster management page, can actually be handling the digest data for that partition. Only digest nodes will be selected as hosts.

    • Other changes: (see 1.13.3 release notes)

    • Other changes: (see 1.13.2 release notes)

    • Other changes: (see 1.13.4 release notes)

    • Improved handling of query restarts to avoid unnecessary restarts in some scenarios.