"unsupported state version" during Nomad server downgrade

State Versioning in Nomad Server

Nomad utilizes an internal state version to manage the Raft state schema. When a server is upgraded to a version that introduces a new storage format or feature, the state version is incremented within the data directory. This mechanism ensures that the cluster state remains consistent with the binary's expected schema.

Rollback Constraints

If a cluster is upgraded and then an attempt is made to revert to a previous binary version, the older version may encounter a state version higher than what it is programmed to handle. This prevents the agent from joining the cluster to avoid potential data corruption.

While job definitions can be exported to facilitate a manual recovery, there is currently no native utility to migrate the state version backward or selectively strip incompatible schema fields without a full state reset.

• What is the recommended strategy for preserving cluster metadata when a state version mismatch prevents a binary rollback?
• Is there a documented method to identify which specific schema changes triggered the version bump to determine if a partial rollback is possible?