Skip to content

Commit b0af79d

Browse files
authored
Add known-issue docs for index/alias name clash bug (#92262)
Relates #91456 Relates #91887
1 parent 48c1447 commit b0af79d

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/reference/release-notes/8.5.0.asciidoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -328,3 +328,10 @@ Packaging::
328328
* When using date range search with format that does not have all date fields (missing month or day)
329329
an incorrectly parsed date could be used. The workaround is to use date pattern with all date fields (year, month, day)
330330
(issue: {es-issue}90187[#90187])
331+
332+
* It is possible to inadvertently create an alias with the same name as an
333+
index in version 8.5.0. This action leaves the cluster in an invalid state in
334+
which several features will not work correctly, and it may not even be possible
335+
to restart nodes while in this state. Upgrade to 8.5.1 as soon as possible to
336+
avoid the risk of this occurring ({es-pull}91456[#91456]). If your cluster is
337+
affected by this issue, upgrade to 8.5.3 to repair it ({es-pull}91887[#91887]).

0 commit comments

Comments
 (0)