FAQ about upgrades
This FAQ covers the business impact and expected duration of engine version and specification upgrades for XXL-JOB instances in Microservices Engine (MSE).
Does upgrading the engine or specifications affect my business?
The impact depends on your instance edition.
Developer Edition instances run on a single node. During an upgrade, job scheduling is fully interrupted until the upgrade completes.
Professional Edition instances run on multiple nodes with disaster recovery. Nodes are upgraded one at a time in a rolling upgrade, so ongoing jobs are not interrupted.
During a rolling upgrade, when a node shuts down, other nodes take over its scheduled jobs within approximately 5 seconds. During this failover window, some jobs may fail to be scheduled. The following table summarizes the impact by edition and job scheduling interval:
| Edition | Job scheduling interval | Impact | Auto-reschedule |
|---|---|---|---|
| Developer Edition | Any | Scheduling interrupted for the full upgrade duration | N/A |
| Professional Edition | > 10 min (for example, daily jobs) | Missed schedules may affect your business | Yes |
| Professional Edition | < 10 min (for example, second-level jobs) | Minimal impact | No |
For jobs with scheduling intervals longer than 10 minutes, XXL-JOB automatically reschedules any jobs that fail during the upgrade. Jobs with shorter intervals are not rescheduled because the next scheduled run occurs soon after the failover window closes.
To minimize upgrade impact, schedule upgrades during off-peak hours when fewer jobs are running.
How long does an engine upgrade take?
| Edition | Estimated duration |
|---|---|
| Developer Edition | Within 2 minutes |
| Professional Edition | 5 to 10 minutes, depending on specifications |