26 April 2016 Releases

Elasticsearch 2.3.2 released

By Clinton Gormley

Today we are pleased to announce the bug fix release of Elasticsearch 2.3.2 based on Lucene 5.5.0. Users who are affected by the issues mentioned in the release notes 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

  • An update to CORS in 2.3.0 broke pre-flight OPTIONS requests, which impacted browser-based applications.
  • Hard allocation decisions, such as moving a shard because the disk is full, were prevented from taking effect unless the index was green.
  • Selecting incorrect concrete indices when restoring a snapshot could result in unwanted indices being restored.
  • The extended_stats aggregation was not accounting for empty buckets correctly.

Marvel

  • Non-elected master nodes all appeared as Offline in the node list.
  • Introduced a timepicker control in the clusters page so you can view older snapshots of Marvel data.

Shield

  • Date math expressions in index names are now resolved before attempting to authorize access to the indices.
  • Active Directory realms did not work unless the url setting was configured.
  • Enabled _cat/indices to be used when Shield is installed.

Watcher

  • All SMTP connection timeouts are now set to two minutes by default to prevent a watch from getting stuck.
  • HTTP headers from responses that contained dots led to exceptions when the HTTP response was stored in the watch history. All dots in any header names are now replaced with underscores. For example, a header called foo.bar becomes foo_bar
  • The Hipchat action now falls back to the default Hipchat color and format if they are not specified at the account level or within the action itself, instead of failing.

Conclusion

Please download Elasticsearch 2.3.2, 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.