Elasticsearch version 7.13.1

edit

Elasticsearch version 7.13.1

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
Engine
  • Fix illegal access on PIT creation for frozen index #73517 (issue: #73514)
Geo
  • Fix typo in Rectangle() error message #73124
Infra/Core
  • Validate that system indices aren’t also hidden indices #72768 (issue: #72631)
Infra/Scripting
  • Add LinkageError to the errors we catch as part of the Painless sandbox #73116
Machine Learning
  • Reduce warning logging from get categories Grok pattern creation #73373
Search
  • Search analyzer should default to configured index analyzer over default #73359 (issue: #73333)
Snapshot/Restore
  • Do not remove write block when unfreezing cold/frozen indices #73368
  • Fix bug with concurrent snapshot and index delete #73456
  • Fix location of repository analyzer API spec #73378