Page History
...
Stop the Windows services and/or Linux processes for each Web and Exec server
Perform backups of the following:
Your Azkaban metadata repository
azkaban.local.properties
for each Web and Exec serverAny other configuration files if you have customized them
Run the installer targeting the existing Azkaban install locations
- Step 1 - upgrade the Azkaban metadata
- Step 2 - upgrade the Azkaban Web Server
- Step 3 - upgrade each Azkaban Executor
Merge any customizations back in from your earlier backups
Start the Azkaban Web and Executor services and/or Linux processes
- Upgrade or merge changes to the Scheduler Integration Scripts as required
Backup your Azkaban Properties and Configuration files
...
Run
RedSchedulerInstaller.exe
to start the upgrade process follow the interactive installer wizardNote title Note For scripted upgrades, the Linux upgrade method described later can also be used on Windows.
- To upgrade the Azkaban metadata and Web Server on this machine, select Install Scheduler and un-check Add scheduler configuration to RED as this configuration has already been added to RED during the original install. If you want to upgrade an Executor on this machine, select Install Executor, as required.
- Choose the existing Azkaban installation location to upgrade.
- Provide the existing RED and Azkaban metadata databases. If you are unsure of the ports and users of your existing servers you can open the azkaban.local.properties file you backed up earlier and extract those details from it.
- Enter your existing server details into the Web Server Configuration and Exec Server Configuration screens ensure you have unchecked the options Install as Windows service as these were already put in place in the original installation.
- Proceed through the rest of the installation wizard and click Install at the end to complete the upgrade of the Azkaban metadata and the Web and Exec Servers.
- Post install you need to manually merge any customizations to the
azkaban.local.properties
and users file as required before starting up your services again.
Upgrade on Linux
...
Command-line Upgrades for Linux or Windows
Like RED, Azkaban is comprised of two distinct parts, the application and the metadata. Some releases may only require one or the other to be upgraded so please refer to the important upgrade messages in the release notes to determine the upgrade requirements.
Azkaban Upgrade Steps
Upgrade the Azkaban Metadata
Upgrade the Azkaban Web Server
Upgrade one or more Azkaban Executor Servers
- Merge any Customizations
- Startup the Services or Processes
Before you begin
It is recommended you perform backups of the following so that any customizations can be merged back in after the upgrade:
Your Azkaban metadata repository
azkaban.local.properties
for each Web and Exec serverAny other configuration files if you have customized them
1. Upgrade the Azkaban Metadata
Ensure the Web Server service or process is stopped.
Perform the Azkaban metadata
...
install by executing the below commands in your
...
command shell
...
in Linux or Windows.
- Stop the Web Server service or process
- Set First, set the environment variables for your Azkaban metadata user and pwd:
Code Block AZ_DB_USER=myuser
AZ_DB_PWD=mypwd
- Then, run the azkaban-installer.jar with the ‘upgrade-schema’ command:code
java.exe
-jar
"azkaban-installer.jar"
upgrade-schema
--database=AZ_REPO
--host=PG_HOST
--port=
5432
--schema=white
--username-var=AZ_DB_USER
--password-var=AZ_DB_PWD
2. Upgrade the Azkaban Web Server
Ensure the Web Server service or process is stopped.
Tip | ||
---|---|---|
| ||
The original response file for each Web and Executor server should still exist in each server's install directory, this can be reused to reapply the same settings as before. If reusing this response file it is important to compare this with the latest version as occasionally new fields are added to the response file for new features, a change in response file fields should be signaled by the important upgrade messages in the release notes. If you have removed or deleted this file then a new one will need to be reconstructed. See the Azkaban Installation section for answer file examples. |
- For Linux: Copy the scheduler .jar file from <RED_install_dir>\Azkaban\azkaban-installer.jar to the host machine and run the following command (with Java 11 JRE):
java -jar azkaban-installer.jar --log-file=./install.log install-server --response-file=web_server_response_file.xml
- For Windows: Open a command prompt and run the following command, replacing the directory location placeholders:
<RED_install_dir>\jre\bin\java -jar <RED_install_dir>\Azkaban\azkaban-installer.jar --log-file=c:\temp\install.log install-server --response-file=<WEB_install_dir>\web_server_response_file.xml
3. Upgrade one or more Azkaban Executor Servers
Ensure the Executor Server service or process is stopped.
- For Linux: Copy the scheduler .jar file from <RED_install_dir>\Azkaban\azkaban-installer.jar to the host machine and run the following command (with Java 11 JRE):
java -jar azkaban-installer.jar
Perform the application upgrade for each Azkaban Web or Executor Server instance.
java -jar azkaban-installer.jarCode Block --log-file=./install.log
install-server --response-file=
executor_server_response_file
.xml - For Windows: Open a command prompt and run the following command, replacing the directory location placeholders:
<RED_install_dir>\jre\bin\java -jar <RED_install_dir>\Azkaban\azkaban-installer.jar --log-file=c:\temp\install.log install-server
--response-file=<EXEC_install_dir>\
executor_server_response_file
.xml
4. Merge any Customizations
Post-install you need to manually merge any customizations to the azkaban.local.properties and users file as required before starting up your services again.
...
5. Startup the Services or Processes
For Windows: Open Services in Windows and restart each Web and Executor service
- For Linux: Run the startup script in the Azkaban install location within the bin directory.
Upgrade the Scheduler Integration Scripts
...
- In RED, open the Azkaban integration script in the script editor such as
wsl_scheduler_publish
under your Host Script objects. - In notepad open the matching script located in the RED installation directory under
<RED install directory>\Administrator\Scripts\wsl_scheduler_publish.ps1
- Copy the contents of the updated script into the RED script editor to overwrite the existing script and Savesave.
Note | ||
---|---|---|
| ||
|
...
If you installed RED to a different folder than when the Windows Azkaban Web Server or Executors were created, then you need to update the ImagePath key in the registry for each Azkaban service.
...