luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: clarify upgrade note on 1.4.0 panics (#16171) 

The panic bug for upgrades with older servers that shipped in 1.4.0 was fixed in
1.4.1, which makes the versions described in the warning in the upgrade guide
misleading. Clarify the upgrade guide.
This commit is contained in:
Tim Gross 2023-02-14 11:26:33 -05:00 committed by GitHub
parent 165791dd89
commit 87b88fd83d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/upgrade/upgrade-specific.mdx
View File

@ -152,14 +152,15 @@ Nomad 1.4.0 initializes a keyring on the leader if one has not been previously
created, which writes a new raft entry. Users have reported that the keyring
initialization can cause a panic on older servers during upgrades. Following the
documented [upgrade process][] closely will reduce the risk of this panic. But
if a server with version 1.4.0 or higher becomes leader while servers with
versions before 1.4.0 are still in the cluster, the older servers will panic.
if a server with version 1.4.0 becomes leader while servers with versions before
1.4.0 are still in the cluster, the older servers will panic.
The most likely scenario for this is if the leader is still on a version before
1.4.0 and is netsplit from the rest of the cluster or the server is restarted
without upgrading, and one of the 1.4.0 servers becomes the leader.
You can recover from the panic by immediately upgrading the old servers.
You can recover from the panic by immediately upgrading the old servers. This
bug was fixed in Nomad 1.4.1.
#### Raft Protocol Version 2 Unsupported