Elasticsearch 1.0.1 and 0.90.12 Released

Today we are happy to announce the release of Elasticsearch 1.0.1 and Elasticsearch 0.90.12.

elasticsearch 1.0.1

Thanks to everyone for the positive feedback on 1.0.0, including the bug reports!  We have responded to the quick feedback with the 1.0.1 release, which is now the current stable release in the 1.0 series.  Details of the changes are available in the release notes. Some of the notable changes are:

We recommend that users of Elasticsearch from all versions upgrade to 1.0.1 and not 1.0.0.  This path will avoid the issue where reading Lucene memory usage could cause excessive CPU usage.

You can download Elasticsearch 1.0.1 here.

elasticsearch 0.90.12

This is the current stable release in the 0.90 series and contains a number of  bug fixes and small enhancements that you can read about in the release notes. Please note that we are decreasing the rate of development of the 0.90.x series of releases so that we can focus our attention on 1.0.x and future releases.  Some of the notable changes are:

  • Memory usage statistics on older, Lucene 3.x segments were using excessive CPU, and they have been disabled.  This will impact node stats results.  We hope to enable them once Lucene 4.7 ships.
  • Fixed a bug where, in rare circumstances, queries could cause an infinite loop.
  • Improved processing of large cluster states, as would happen with a large number of mappings, on non-master nodes.
  • Fixed a bug where the get field mapping API call could return incorrect results.

We recommend that users of Elasticsearch from the 0.20.x series or earlier upgrade to 0.90.12 and not 0.90.11, or 1.0.1.  This path will avoid the issue where getting Lucene memory usage could cause excessive CPU usage.

You can download Elasticsearch 0.90.12 here.