Humio Server 1.24.2 LTS (2021-04-19)
| Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
|---|---|---|---|---|---|---|---|
| 1.24.2 | LTS | 2021-04-19 | Cloud | 2022-04-30 | No | 1.16.0 | No |
Hide file hashes
| JAR Checksum | Value |
|---|---|
| MD5 | 69a6ef22d7f295f807ceef46c8c0c6d1 |
| SHA1 | 6284ee05bd7c583044f6620f385864a3be3bab84 |
| SHA256 | cc648f1c4efe01d20e9f93a77b1892291077ae76339d1b5dcbc0e504f9975e25 |
| SHA512 | 54c60624a5c0ef19c12fcda05b4fecbe8ddf626246c3160d90f29cc76143dfbe4b07f7d884616699486848f0e7b8c519c0e1d5f5dd3e2be3e8b0a6f49fe960c5 |
These notes include entries from the following previous releases: 1.24.0, 1.24.1
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.
Fixed in this release
Other
Removed the
QUERY_QUOTA_EXCEEDED_PENALTYconfig (introduced in 1.19.0).Fixed an issue on the search page that prevented the event list from scrolling correctly.
Fixed a bug where ingestOnly nodes could not start on a more recent version that the statefull nodes in the cluster
Fixed an issue which prevented Safari users from seeing alert actions
Fixed an issue where cost spent in a long-running query got accounted as spent "now" when the query ended in terms of Query Quota
Fixed an issue which caused problems with forward/backward compatibility of LanguageVersion in GraphQL
Major changes: 1.23.0 and 1.23.1.
Fixed an issue where a repository with very high number of datasources could trigger an error writing an oversized message to kafka from the ingest-reader-leader thread
The query scheduler now prioritizes new queries started by a user based on the cumulative cost of recent queries started by that user. Added new config
QUERY_SPENT_FACTORwith the default value 0.5, which defines the weight of recent query costs when scheduling. Higher values mean that users with high recent query costs will see their queries penalized harder in the scheduling.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
Fixes an issue where the user would get stuck in infinite loading after having been invited into an organization
Fixed a scrolling issues on the Kafka cluster admin page
Allow reverse proxies using 10s as timeout to work also for a query that takes longer than that to initialize
Reduced off-heap memory usage