Add Restore UUID Index Setting #56930
Conversation
Pre-requesite for #50278 to be able to uniquely identify index metadata by its version fields and UUIDs when restoring into closed indices.
original-brownbear
added
>non-issue
:Distributed Indexing/Distributed
|
Pinging @elastic/es-distributed (:Distributed/Distributed) |
elasticmachine
added
the
Team:Distributed (Obsolete)
ywelsch
left a comment
ywelsch
left a comment
There was a problem hiding this comment.
I wonder if we should generalize this to an index.history.uuid (which is also updated on dangling indices import, as well as whenever we run the unsafe bootstrap command). This makes this also more generally useful to characterize the identity of the index metadata.
| settings.remove(IndexSettings.INDEX_SOFT_DELETES_SETTING.getKey()); | ||
| settings.remove(IndexMetadata.SETTING_INDEX_VERSION_CREATED.getKey()); | ||
| settings.remove(IndexMetadata.SETTING_INDEX_UUID); | ||
| settings.remove(IndexMetadata.SETTING_RESTORE_UUID); |
There was a problem hiding this comment.
Should we remove this setting on clone/split/shrink as well?
There was a problem hiding this comment.
Jup makes sense to me => done.
|
Jenkins run elasticsearch-ci/2 (random known aggs failure) |
|
Jenkins run elasticsearch-ci/bwc |
|
Thanks @ywelsch, I renamed the setting as suggested and added the functionality to dangling index import and unsafe bootstraps now. |
|
Thanks Yannick! |
4 participants
Pre-requesite for #50278 to be able to uniquely identify index metadata by
its version fields and UUIDs when restoring into closed indices.
See related discussion here: #50278 (comment)