Elasticsearch version 7.13.2

edit

Elasticsearch version 7.13.2

edit

Also 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.

  • Parsing a request when the last element in an array is filtered out (for instance using _source_includes) fails. This is due to a bug in Jackson parser. Fixed in Elasticsearch 8.6.1 (#91456)
  • The deprecated index.mapper.dynamic setting can break your cluster. It can only be set using the Update index settings API. Symptoms include nodes failing to start or shards failing to allocate. Do not use this setting in versions prior to 7.17.22. The bug is fixed in 7.17.22. (issue: #109160)

Bug fixes

edit
Aggregations
  • Add setting to disable aggs optimization #73620 (issue: #73426)
Cluster Coordination
  • Write next cluster state fully on all failures #73631
Features/ILM+SLM
  • Always handle non-complete AsyncActionStep execution #73796 (issue: #73794)
  • Copy all execution state in CopyExecutionStateStep #73792 (issues: #64883, #73791)
Features/Ingest
  • Preserve field mappings from user agent processor when ECS is disabled #73783 (issue: #73780)
Infra/Core
  • Resolve concrete associated indices when resetting features #73017 (issue: #72363)
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