Fix Job Schedules after 2022.3 Upgrade¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
In the 2022.3 release, we unified our use of time zones on the Alation server. We made UTC the default server time zone and adjusted various schedules so they would continue to run at the same time. Unfortunately, we failed to adjust the schedule for some jobs, causing them to run eight hours earlier than they should. This affected the schedule for:
Metadata extraction (MDE)
Query log ingestion (QLI)
Determine If You Were Affected¶
To determine if you were affected by this issue, check the schedule for MDE, QLI, and profiling on your data sources. If they appear to be scheduled eight hours sooner than you would expect, you may be affected.
How To Fix the Problem¶
If you’re an Alation Cloud Service customer and you know you were affected by this issue contact Support to request the fix.
If you’re using an on-premises instance of Alation and you were affected, you can fix the issue in several ways:
Alation 2023.1.4 contains a built-in script that can be run to fix the issue.
For earlier versions of Alation, contact Alation Support to get a copy of the script, as it isn’t available in the installation directory yet.
Update the schedules manually. This can be a good solution if you only have a few schedules to change.
Run the Script¶
If you’ve already fixed your schedules manually, there is no need to run the script. The script will shift the affected schedules eight hours later, back to their original time. You can run the script at any time after upgrading to 2022.3 or later.
To run the job schedule fix in 2023.1.4 for on-premises instances of Alation:
Use SSH to connect to the Alation server.
Enter the Alation shell using the following command:
sudo /etc/init.d/alation shell
Make a backup of the Alation database. See Create Backups Manually for help making a backup.
Change into the Django directory:
Enter the Django shell:
python manage.py shell
Run the following statement:
from rosemeta.one_off_scripts.update_job_timezones_utc import *; main()
When the script has run successfully, the number of schedules that were updated will be printed to the console like this:
Updating 3 schedules.
If no schedules needed to be updated because they were already correct, the script will say zero schedules were updated.
Updating 0 schedules.
If the script produces errors, contact Alation Support.
When you are done, exit the Django shell:
Exit the Alation shell: