index.data_path is mutable on closed replicated indices #44899
Labels
:Distributed Indexing/Store
Issues around managing unopened Lucene indices. If it touches Store.java, this is a likely label.
team-discuss
Comments
DaveCTurner
added
:Distributed Indexing/Store
|
Pinging @elastic/es-distributed |
|
There's a more general question about support for shared data paths over at #34446 that subsumes this issue, so I'm closing this with a link to the other issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Today if you are using
index.data_pathto define a custom data path for an index then it is possible to adjust this setting while the index is closed. However, now that closed indices are replicated (#33888) this seems to be able to get you into a royal mess: if you adjust this setting but do not manually move the shard data to match before Elasticsearch notices (e.g. it starts trying to perform a peer recovery for a shard of this closed index) then shards will fail, and it may require significant manual work to get everything up and running again.The text was updated successfully, but these errors were encountered: