Published on 2021-04-12 00:00:00

Humio 1.24.1

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.24.1

Stable

2021-04-12

2022-04-06

1.16.0

No

No

JAR Checksum

Value

MD5

b7fec8d3a5c0b521a371dbeb6e56d8b2

SHA1

fbabef325eaaf1bd0a3052f51497f00779efad5f

SHA256

223e48fe647fc681456b47cad81d0fca5936d6283791b2a41fa4c8dc199c1c76

SHA512

51663220d67bb25f67b7e44837e84c87c36c3f24da69918b1a6978fc751543a2f1f25f49f166681def7a0276881907b284a52bb302fa6d745d7b16859d3f7d96

TGZ Checksum

Value

MD5

b7fec8d3a5c0b521a371dbeb6e56d8b2

SHA1

fbabef325eaaf1bd0a3052f51497f00779efad5f

SHA256

223e48fe647fc681456b47cad81d0fca5936d6283791b2a41fa4c8dc199c1c76

SHA512

51663220d67bb25f67b7e44837e84c87c36c3f24da69918b1a6978fc751543a2f1f25f49f166681def7a0276881907b284a52bb302fa6d745d7b16859d3f7d96

Important Information about Upgrading

Beginning with version 1.17.0, if your current version of Humio is not directly able to upgrade to the new version, you will get an error if you attempt to start up the incompatible version. The 1.24.1 release is only compatible with Humio release 1.16.0 and newer. This means that you will have to ensure that you have upgraded at least to 1.16.0 before trying to upgrade to 1.24.1. In case you need to do a rollback, this can also ONLY happen back to 1.16.0 or newer. Rolling directly back to an earlier release can result in data loss.

Change Log

  • Ensure that if the Kafka leader loop thread dies, it kills the Humio process. In rare cases it was possible for this thread to die, leaving the node incapable of performing digest work

  • Allow reverse proxies using 10s as timeout to work also for a query that takes longer than that to initialize

  • Fixes an issue where the user would get stuck in infinite loading after having been invited into an organization

  • Fixed a bug where ingestOnly nodes could not start on a more recent version that the statefull nodes in the cluster