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

Merge pull request #5815 from hashicorp/f-downgrade-docs

Browse source 
Add warning docs around downgrades
This commit is contained in:
Preetha 2019-06-12 10:39:43 -05:00 committed by GitHub
parent 54d544e874 cd813e50ec
commit 71ba7eb9cb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
website/source/guides/upgrade/index.html.md
View file

@ -17,6 +17,13 @@ communication with Servers. As such, care should be taken to properly
upgrade Nomad to ensure minimal service disruption. Unsafe upgrades can
cause a service outage.
~> **Downgrade Warning!** We currently do not support safely downgrading
Nomad servers. This is due to the fact that the data directory
contains transaction logs which may not safely apply after a downgrade. To downgrade
a Nomad server, its data directory must be wiped out. In general, Client downgrades are
safe to do, however we recommend checking the [upgrade specific](/guides/upgrade/upgrade-specific.html)
page which will highlight versions where a client downgrade is not supported.
## Upgrade Process
For upgrades we strive to ensure backwards compatibility. For most upgrades, the

5
website/source/guides/upgrade/upgrade-specific.html.md
View file

@ -107,6 +107,11 @@ unchanged.
Since HCL2 uses dotted object notation for interpolation users should
transition away from variable names with multiple consecutive dots.
### Downgrading clients
Due to the large refactor of the Nomad client in 0.9, downgrading to a
previous version of the client after upgrading it to Nomad 0.9 is not supported.
To downgrade safely, users should erase the Nomad client's data directory.
## Nomad 0.8.0
### Raft Protocol Version Compatibility