Update Alation to 2024.3

Customer Managed Applies to customer-managed instances of Alation

2024.3 Update Version Dependencies

Alation supports a direct update to version 2024.3 from the following previous versions:

  • 2024.1.x

  • 2023.3.x

The full list of new features and bug fixes in 2024.3 is available in Release Notes 2024.3 (General Availability).

2024.3 Release-Specific Information

The 2024.3 release includes a bug fix for Alation Analytics where Steward updates in term objects made through Bulk Actions were not appearing in the Alation Analytics database. The solution includes a migration script in the update package that resets the ETL checkpoint for terms. No action is needed from the Server Admin side. After the update, the ETL process for terms will restart from the beginning. Given Alation Analytics’ ETL capacity to process only six months of data per ETL run and depending on the volume of terms data, several ETL cycles may be necessary to fully update the terms data. This could result in a delay in reflecting the latest changes to terms.

Update from Version 2023.1.x or Older

Direct update to 2024.3 is not supported from version 2023.1.x or older versions. First, update Alation to a version that supports the direct update to 2024.3 and then perform a second update to 2024.3.

Update Known Issues

Reset Postgres Password

If you have a password set on the internal PostgreSQL database (Rosemeta), the update will result in an error similar to the following:

WARN: unable to check pg-1: [DbConnectError] unable to connect to 'dbname='postgres' port=5432':
FATAL: password authentication failed for user "postgres"
password retrieved from file "/home/postgres/.pgpass"
ERROR: [056]: unable to find primary cluster - cannot proceed

The update process requires that the password on the internal PostgreSQL database should be cleared for the time of the update. The password can be set again after the update is completed. On how to set the Postgres password, see Set Password for Internal PostgreSQL Instances.

Use Cluster Splitting for HA Pair Update

The Alation update of an HA pair without splitting the cluster fails. We recommend upgrading HA instances using the cluster splitting upgrade method until this issue is resolved.

Select Your Update Instruction

Depending on your current version, the update may require upgrading the Alation internal database (Postgres) to version 16.2. Use the instructions specific to the release you are updating from: