Grayscale release
1. Purpose
The gray release is to reduce the impact on the existing business during the upgrade process. After upgrading an Executor, first verify whether there is no problem, and then gradually upgrade in batches.
At the same time, during the upgrade process, do not affect the operation of other original Executor jobs.
The gray release requires at least 2 Executors in the domain.
2. When do you need to publish in grayscale
- Changed existing job code
- New assignments added
3. Process
-
Log in to the Saturn console and set the "priority executor" of all jobs under the domain to one of the executors, assuming it is executor_B .
-
At the right time (for example, by judging by saturn console that all jobs are in the complete state, or all jobs are being executed on executor_B), executor_A is taken offline.
-
Upgrade executor_A. Including replacement job package, and Executor package (if you need to upgrade the execuotor), and restart. Observe that executor_A goes online on the console .
Note: The current version does not support job hot deployment, so you must first stop and then replace the package.
-
In the Saturn console, change the "priority executor" of all jobs under the domain to new executor_A
-
Verify the running result of executor_A .
-
If everything is normal, upgrade executor_B . Including replacement job package, and Executor package (if you need to upgrade the execuotor), and restart.
-
In the Saturn console, cancel the "priority executor" option for all jobs under the domain, so that all job fragments are evenly distributed to all executors.