Upgrading Document Engine
We recommend always running the latest version of Document Engine, as each version introduces new features and performance improvements. Additionally, we always verify that the release process is seamless when upgrading to the newest version from the last major release. If you’re using an older version, make sure to upgrade one major version at a time.
Example: If the latest version is 1.6.1 and you’re running 1.4.4, upgrade to 1.5.x first, and only then to 1.6.1.
We recommend always going through the upgrade process in a non-production environment first.
The process of upgrading to a new version of Document Engine varies depending on whether you’re running a single instance or multiple instances.
In a single-node deployment, shut down your Document Engine instance and start a new one using the new Docker image.
In a multi-node setup, the simplest approach is to scale down your Document Engine deployment to only one instance and then upgrade it. Then, once it’s up and running, start the other instances with the new version.
If you can’t accept downtime, you can also follow a more complex upgrade scenario:
Drain traffic from a single instance and make sure that no requests are directed to it.
Upgrade the instance to a new version. Don’t direct traffic to that instance yet.
Once that instance is up and running, continue with other instances after you reach a number that’s sufficient for serving your user traffic. Note that, at this moment, all users will still be served by instances running the old version.
Switch all traffic to instances running the new version.
Continue with the upgrade for the rest of the instances. Once an instance is running the new version, you can immediately add it to the group serving the user traffic.
While this approach is more complex and requires a deployment infrastructure that provides control over which instances are serving user traffic, it allows you to upgrade without downtime.