Elasticsearch version 7.10.1
editElasticsearch version 7.10.1
editAlso see Breaking changes in 7.10.
Known issues
edit-
In Elasticsearch 7.10.0 there were several regressions around loading nested documents. These have been addressed in Elasticsearch 7.10.2.
-
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.
Bug fixes
edit- Allocation
-
- Fix NPE in toString of FailedShard #64770
- CCR
-
- Stop renew retention leases when follow task fails #65168
- CRUD
- Cluster Coordination
- EQL
- Features/ILM+SLM
-
- Fix SetSingleNodeAllocateStep for data tier deployments #64679
- Features/Watcher
- Geo
- Infra/Core
- Infra/Scripting
- Machine Learning
-
- Extract dependent variable’s mapping correctly in case of a multi-field #63813
- Fix bug with data frame analytics classification test data sampling when using custom feature processors #64727
- Fix custom feature processor extraction bugs around boolean fields and custom one_hot feature output order #64937
- Protect against stack overflow while loading data frame analytics data #64947
- Fix a bug where the peak_model_bytes value of the model_size_stats object was not restored from the anomaly detector job snapshots #1572
- Mapping
- SQL
-
- Fix the return type problem in the sign function #64845
- Search
- Snapshot/Restore