Elasticsearch version 7.11.1

edit

Elasticsearch version 7.11.1

edit

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

  • 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)

Enhancements

edit
Features/Indices APIs
Features/Stats
  • Add index creation version stats to cluster stats #68141
Snapshot/Restore
  • Improve shard evictions in searchable snapshot cache service #67160 (issues: #66730, #66958)
  • Make blob cache have async durability #66687

Bug fixes

edit
Authentication
Cluster Coordination
  • Determine data role based on convention #66933 (issue: #66000)
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 the isAcknowledged flag on the response #67591 (issue: #53111)
  • Skip rollover if the data stream is rolled over already #67778 (issue: #67777)
Features/Indices APIs
  • Fix exception when validating composable template with no template #67310 (issue: #66949)
Features/Ingest
  • Fix parsing empty value with brackets failed in dissect ingest processor #65524 (issue: #65080)
Features/Stats
  • Allow reading of /proc/meminfo for JDK bug workaround #68742
  • Workaround for JDK bug with total memory on Debian 8 #68542 (issues: #66629, #66885)
Geo
  • Add support for distance_feature query for runtime geo_point field #68094 (issue: #67910)
Infra/Scripting
  • Remove leniency for casting from a def type to a void type in Painless #66957 (issue: #66175)
Machine Learning
  • Ensure mappings are up to date before reverting state #68746
Network
  • Fix AbstractClient#execute Listener Leak #65415 (issue: #65405)
Packaging
  • Fix an error that occurs while starting the service in Windows OS under a path with a space in it #61895 (issue: #61891)
  • Fix an issue with MSI installation on Windows that prevents Elasticsearch starting #402 (issue: #68914)
Recovery
  • Check graveyard on dangling index import #67687
SQL
  • Fix elasticsearch-sql-cli under Docker #67737 (issue: #57744)
  • Fix the MINUTE_OF_DAY() function that throws exception when used in comparisons #68783 (issues: #67872, #68788)
Snapshot/Restore
  • Reduce number of cache/prewarm threads #67021
  • Adjust encoding of Azure block IDs #68957 (issue: #66489)