Product release

Elasticsearch 2.3.3 released

By
Clinton Gormley

Today we are pleased to announce the bug fix release of Elasticsearch 2.3.3 based on Lucene 5.5.0. All users of 2.3.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:

Elasticsearch

  • Trying to read completion stats on an already closed index reader could result in a JVM crash. We have had no reports of this from users, but it is advisable to upgrade in order to avoid this bug, which was introduced in Elasticsearch 2.3.0.
  • CORS now allows same origin requests correctly, works with HTTP compression enabled, and no longer tries to distinguish browser requests from others.
  • Using wildcards to select fields for highlighting now restricts the field list to those that can be highlighted, avoiding exceptions when trying to highlight geo fields.
  • Geo-shape CONTAINS relationship now works correctly.
  • Elasticsearch no longer leaks thread locals when running in certain web containers.

Marvel

  • No longer logs exceptions when node stats are temporarily empty.

Shield

  • Fixed the /_shield/realm/{realms}/_cache/clear REST endpoint. This endpoint is deprecated and /_shield/realm/{realms}/_clear_cache should be used going forward.

Conclusion

Please download Elasticsearch 2.3.3, try it out, and let us know what you think on Twitter (@elastic) or in our forum. You can report any problems on the GitHub issues page.