Upgrading a Cluster#

Repeat this procedure for all nodes of the cluster, one at a time:

1. Stop the server by putting it into Lame Duck Mode
2. Replace the binary or Docker image with the new version.
3. Restart the server.
4. Wait until the /healthz endpoint returns HTTP 200 OK before moving on to the next cluster node.

Downgrading#

Although the NATS server goes through rigorous testing for each release, there may be a need to revert to the previous version if you observe a performance regression for your workload. The support policy for the server is the current release as well as one patch version release prior. For example, if the latest is 2.8.4, a downgrade to 2.8.3 is supported. Downgrades to earlier versions may work, but is not recommended.

Fortunately, the downgrade path is the same as the upgrade path as noted above. Swap the binary and do a rolling restart.