This article refers to our hosted Elasticsearch offering by an older name, Elastic Cloud. Please note that Elastic Cloud is now known as the Elasticsearch Service, which is not the same as the Amazon Elasticsearch Service. Visit our AWS Elasticsearch comparison page to learn more.
Today we are pleased to announce the bug fix release of Elasticsearch 2.3.4 based on Lucene 5.5.0. All users of 2.x are advised to upgrade. This release is already available on Elastic Cloud, our Elasticsearch-as-a-service platform.
Latest stable release:
Full details of the changes in this release are available in the release notes listed above, but some of the more important changes are mentioned below:
- The transaction log can be corrupted following a disk full exception and several attempts to recover the shard. This has been reported once in the wild.
Higlighting a query with the plain highlighter in the presence of a
geo_pointquery now works correctly.
- Stale monitoring data can now be viewed.
- Relocating shards are no longer counted as unassigned.
- The index search wrapper is now a singleton to avoid a memory leak when repeatedly creating and deleting indices.