Skip to content

Fail start on obsolete indices documentation #37786

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Jan 31, 2019
Merged

Fail start on obsolete indices documentation #37786

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9348907
Fail start on obsolete indices documentation
henningandersen Jan 23, 2019
0496019
Merge remote-tracking branch 'origin/master' into fail_on_obsolete_in…
henningandersen Jan 24, 2019
9525742
Fail start on obsolete indices documentation
henningandersen Jan 24, 2019
e768136
Merge remote-tracking branch 'origin/master' into fail_on_obsolete_in…
henningandersen Jan 30, 2019
eaa652b
Fail start on obsolete indices documentation
henningandersen Jan 30, 2019
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
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ See also <<release-highlights>> and <<es-release-notes>>.
* <<breaking_70_snapshotstats_changes>>
* <<breaking_70_restclient_changes>>
* <<breaking_70_low_level_restclient_changes>>
* <<breaking_70_node_start>>

[float]
=== Indices created before 7.0
Expand Down Expand Up @@ -58,3 +59,4 @@ include::migrate_7_0/scripting.asciidoc[]
include::migrate_7_0/snapshotstats.asciidoc[]
include::migrate_7_0/restclient.asciidoc[]
include::migrate_7_0/low_level_restclient.asciidoc[]
include::migrate_7_0/node_start.asciidoc[]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given that the documentation for the different node modes is under the node module (see https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html), perhaps name this node.asciidoc and the label above <<breaking_70_node_changes>>

19 changes: 19 additions & 0 deletions docs/reference/migration/migrate_7_0/node_start.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
[float]
[[breaking_70_node_start]]
=== Node start up

[float]
==== Node start up detects and fails on obsolete indices
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about the "obsolete" word here. How about: "Nodes with left-behind data or metadata refuse to start"

To avoid importing obsolete dangling indices, node start up will fail in following two situations:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An alternative formulation:

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 startup in 7.0.


* Starting up a non-data node that has shard data (e.g. dedicated master node or coordinating-only node)
* Starting up a non-data, non-master node that has index metadata.

This situation should only occur if the settings `node.data` or `node.master` have been changed. Following are the primary
situations to be aware of:

* A node previously configured as `node.data=true` and `node.master=true` is changed to `node.data=false`
* A node previously configured as `node.data=false` and `node.master=true` is changed to `node.master=false`
* A node previously configured as `node.data=true` and `node.master=false` is changed to `node.data=false` and `node.master=true`

Beware that such changes done prior to the 7.0 upgrade could prevent starting nodes.