DolphinScheduler Upgrade Documentation

Back-Up Previous Version's Files and Database

Stop All Services of DolphinScheduler

sh ./script/stop-all.sh

Download the Latest Version Installation Package

• download the latest version of the installation packages.
• The following upgrade operations need to be performed in the new version's directory.

Database Upgrade

• If using MySQL as the database to run DolphinScheduler, please config it in ./bin/env/dolphinscheduler_env.sh, change username and password to yours, and add MYSQL connector jar into lib dir ./tools/libs, here we download mysql-connector-java-8.0.16.jar, and then correctly configure database connection information. You can download MYSQL connector jar from here. Otherwise, PostgreSQL is the default database.

  export DATABASE=${DATABASE:-mysql}
  export SPRING_PROFILES_ACTIVE=${DATABASE}
  export SPRING_DATASOURCE_DRIVER_CLASS_NAME=com.mysql.cj.jdbc.Driver
  export SPRING_DATASOURCE_URL=jdbc:mysql://127.0.0.1:3306/dolphinscheduler?useUnicode=true&characterEncoding=UTF-8
  export SPRING_DATASOURCE_USERNAME={user}
  export SPRING_DATASOURCE_PASSWORD={password}
  

• Execute database upgrade script:

  sh ./tools/bin/upgrade-schema.sh

Backend Service Upgrade

Modify the Content in conf/config/install_config.conf File

• Standalone Deployment please refer to the Standalone-Deployment.
• Cluster Deployment please refer to the Cluster-Deployment.

Masters Need Attentions

Create worker group in 1.3.1 version has a different design:

• Before version 1.3.1 worker group can be created through UI interface.
• Since version 1.3.1 worker group can be created by modifying the worker configuration.

When Upgrade from Version Before 1.3.1 to 1.3.2, the Below Operations are What We Need to Do to Keep Worker Group Configuration Consist with Previous

1. Go to the backup database, search records in t_ds_worker_group table, mainly focus id, name and IP three columns.

2. Modify the worker configuration in conf/config/install_config.conf file.

Assume bellow are the machine worker service to be deployed:

To keep worker group config consistent with the previous version, we need to modify workers configuration as below:

#worker service is deployed on which machine, and also specify which worker group this worker belongs to. 
workers="ds1:service1,ds2:service2,ds3:service2"

The Worker Group has Been Enhanced in Version 1.3.2

Workers in 1.3.1 can't belong to more than one worker group, but in 1.3.2 it's supported. So in 1.3.1 it's not supported when workers="ds1:service1,ds1:service2", and in 1.3.2 it's supported.

Execute Deploy Script

`sh install.sh`