Today we are pleased to announce bug fix releases of Elasticsearch 2.4.2 and Elasticsearch 1.7.6. This is the final release in the 1.x series. These releases are already available for deployment on Elastic Cloud, our Elasticsearch-as-a-service platform.
Full details of the changes in this release are available in the release notes listed above, but there are a few important changes in Elasticsearch 2.4.2 which are worth mentioning:
Using wildcards when deleting indices beginning with
-could result in the unexpected deletion of other indices. For instance, trying to delete
-foo*would delete all indices except those beginning with
not_analyzedfields was a no-op, but its removal in 2.4.0 prevented users who had specified it from upgrading. We’ve downgraded the exception to a deprecation warning.
- Tribe nodes unneccesarily processed the whole cluster state on every cluster state update, including shard allocation changes. Now Tribe nodes just process the relevant parts.
- The ShardActiveResponseHandler was holding onto the entire cluster state when really it just needs to know the cluster state version. This could result in excesive memory use on unresponsive clusters.
Please download Elasticsearch 2.4.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.