Elasticsearch version 7.11.1
editElasticsearch version 7.11.1
editAlso see Breaking changes in 7.11.
Known issues
edit-
Snapshot and restore: If an index is deleted while the cluster is concurrently taking more than one snapshot then there is a risk that one of the snapshots may never complete and also that some shard data may be lost from the repository, causing future restore operations to fail. To mitigate this problem, set
snapshot.max_concurrent_operations: 1
to prevent concurrent snapshot operations:PUT _cluster/settings { "persistent" : { "snapshot.max_concurrent_operations" : 1 } }
This issue is fixed in Elasticsearch versions 7.13.1 and later. It is not possible to repair a repository once it is affected by this issue, so you must restore the repository from a backup, or clear the repository by executing
DELETE _snapshot/<repository name>/*
, or move to a fresh repository. For more details, see #73456.
Enhancements
edit- Features/Indices APIs
- Features/Stats
-
- Add index creation version stats to cluster stats #68141
- Snapshot/Restore
Bug fixes
edit- Authentication
- Cluster Coordination
- Features/ILM+SLM
-
- Check if delete phase has actions #66664 (issue: #65847)
- Fix handling of configurations with a combination of both maximum and expire-after retention #68352
- Fix searchable snapshot action to wait for the restored index #68309 (issue: #67879)
-
Ignore
clusterChanged
events if state not recovered #67507 (issue: #67506) -
ShrinkStep
ignores theisAcknowledged
flag on the response #67591 (issue: #53111) - Skip rollover if the data stream is rolled over already #67778 (issue: #67777)
- Features/Indices APIs
- Features/Ingest
- Features/Stats
- Geo
- Infra/Scripting
- Machine Learning
-
- Ensure mappings are up to date before reverting state #68746
- Network
- Packaging
- Recovery
-
- Check graveyard on dangling index import #67687
- SQL
- Snapshot/Restore