Elasticsearch version 7.13.2
editElasticsearch version 7.13.2
editAlso see Breaking changes in 7.13.
Known issues
edit-
Frozen tier: (Windows only) The frozen data tier relies on multiple caching mechanisms to speed up access to searchable snapshot files. One of these caches uses sparse files to avoid creating large files on disk when it is not strictly required. A bug prevented files from being created with the right options to enable sparse support on Windows, leading Elasticsearch to create potentially large files that can end up consuming all the disk space.
This issue is fixed in Elasticsearch versions 7.15.2 and later. There is no known workaround for earlier versions. Filesystems that enable sparse files by default are not affected. For more details, see #79371.
-
Snapshot and restore: If a running snapshot is cancelled while a previously-started snapshot is still ongoing and a later snapshot is enqueued then there is a risk that some shard data may be lost from the repository. This will cause 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.14.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 #75598.
Bug fixes
edit- Aggregations
- Cluster Coordination
-
- Write next cluster state fully on all failures #73631
- Features/ILM+SLM
- Features/Ingest
- Infra/Core
- Search
-
- Fix error when fetching values for parent ID join field #73639
- Snapshot/Restore
-
- Fix repo name at allocation time #73669
- Monitoring
-
-
Add ability for
monitoring_user
role to read from metricbeat-* #71233
-
Add ability for