7abeaba8bb
Downgrading an Elasticsearch node to an earlier version is unsupported, because we do not make any attempt to guarantee that a node can read any of the on-disk data written by a future version. Yet today we do not actively prevent downgrades, and sometimes users will attempt to roll back a failed upgrade with an in-place downgrade and get into an unrecoverable state. This change adds the current version of the node to the node metadata file, and checks the version found in this file against the current version at startup. If the node cannot be sure of its ability to read the on-disk data then it refuses to start, preserving any on-disk data in its upgraded state. This change also adds a command-line tool to overwrite the node metadata file without performing any version checks, to unsafely bypass these checks and recover the historical and lenient behaviour. |
||
|---|---|---|
| .. | ||
| certgen.asciidoc | ||
| certutil.asciidoc | ||
| index.asciidoc | ||
| migrate-tool.asciidoc | ||
| node-tool.asciidoc | ||
| saml-metadata.asciidoc | ||
| setup-passwords.asciidoc | ||
| shard-tool.asciidoc | ||
| syskeygen.asciidoc | ||
| users-command.asciidoc | ||