Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail start on obsolete indices documentation #37786

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/reference/migration/migrate_7_0.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,7 @@ See also <<release-highlights>> and <<es-release-notes>>.
* <<breaking_70_restclient_changes>>
* <<breaking_70_low_level_restclient_changes>>
* <<breaking_70_logging_changes>>
* <<breaking_70_node_changes>>

[float]
=== Indices created before 7.0
Expand Down Expand Up @@ -60,3 +61,4 @@ include::migrate_7_0/snapshotstats.asciidoc[]
include::migrate_7_0/restclient.asciidoc[]
include::migrate_7_0/low_level_restclient.asciidoc[]
include::migrate_7_0/logging.asciidoc[]
include::migrate_7_0/node.asciidoc[]
15 changes: 15 additions & 0 deletions docs/reference/migration/migrate_7_0/node.asciidoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
[float]
[[breaking_70_node_changes]]
=== Node start up

[float]
==== Nodes with left-behind data or metadata refuse to start
Repurposing an existing node by changing node.master or node.data to false can leave lingering on-disk metadata and
data around, which will not be accessible by the node's new role. Beside storing non-accessible data, this can lead
to situations where dangling indices are imported even though the node might not be able to host any shards, leading
to a red cluster health. To avoid this,

* nodes with on-disk shard data and node.data set to false will refuse to start
* nodes with on-disk index/shard data and both node.master and node.data set to false will refuse to start

Beware that such role changes done prior to the 7.0 upgrade could prevent node start up in 7.0.