Published on 2021-02-01 00:00:00

Humio 1.20.1

Minor Bug Fix Release

Version

Type

Release Date

End of Support

Upgrades From

Data Migration

Config. Changes

1.20.1

Stable

2021-02-01

2022-01-28

1.16.0

No

No

JAR Checksum

Value

MD5

5f2ccaea9f97572ec047be936d7ff0de

SHA1

5e434cc0df8b437a3974be645e80c3f2c56ec78a

SHA256

74f2fcf3d5d2bc5b1e5830d98a03512395ac7beb6456bf754e69e48e89e1d7cf

SHA512

16a58326069b3dd9e401688627e62e825249654501f63c939d245c6b501bd683c7682a634f9cb0265c17029ac8b7cdf038e57daa27a57478980115bce18c53ce

TGZ Checksum

Value

MD5

5f2ccaea9f97572ec047be936d7ff0de

SHA1

5e434cc0df8b437a3974be645e80c3f2c56ec78a

SHA256

74f2fcf3d5d2bc5b1e5830d98a03512395ac7beb6456bf754e69e48e89e1d7cf

SHA512

16a58326069b3dd9e401688627e62e825249654501f63c939d245c6b501bd683c7682a634f9cb0265c17029ac8b7cdf038e57daa27a57478980115bce18c53ce

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.20.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.20.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

  • Minor fix to Humio internal JSON logging when using the configuration HUMIO_LOG4J_CONFIGURATION=log4j2-json-stdout.xml