Skip to content

Commit bc732a0

Browse files
authored
Add release highlight for replicated closed indices on 7.2.0 (#43530)
1 parent 28c5d6b commit bc732a0

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

docs/reference/release-notes/highlights-7.2.0.asciidoc

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,27 @@ summarize your data and store it in a new index. Alternatively, you can use
2121
the transforms.
2222

2323
// end::notable-highlights[]
24+
25+
// tag::notable-highlights[]
26+
[float]
27+
==== Closed indices are now replicated
28+
29+
Elasticsearch 7.2.0 brings better support for closed indices by allowing
30+
shards of closed indices to be replicated. As soon as an index is closed,
31+
Elasticsearch takes care of safely tearing down the "opened" shards before
32+
reinitializing them as "closed" shards, which require much less resources
33+
while still providing the ability for shards to be promoted as primaries or
34+
to be recovered from peer. The data is also automatically replicated by the
35+
cluster to ensure that enough shard copies are safely kept around at all
36+
times (configurable with `index.number_of_replicas`).
37+
38+
In addition to that, it is now possible to snapshot closed indices using
39+
the <<modules-snapshots,Snapshot/Restore API>>. To include a closed index
40+
when creating a snapshot on Elasticsearch 7.2+, the `expand_wildcards`
41+
parameter must be explicitly set to either `all` or `closed` .
42+
43+
Note that only indices closed in Elasticsearch 7.2+ are automatically
44+
replicated. Indices closed on previous versions of Elasticsearch will
45+
remain non replicated unless they are opened and closed again in 7.2+.
46+
47+
// end::notable-highlights[]

0 commit comments

Comments
 (0)