How the retirement of Elasticsearch 2 will affect you - Noteworthy at Compose

Published

This is your weekly summary of Compose news for those changes and updates which can make your life easier. In this edition, Elasticsearch 2.4.6 is being retired at Compose and what it means to you. We also take a look at the past week's Compose Articles.

Elasticsearch 2.x Retirement Plans

If you aren't running Elasticsearch 2.4.6 or earlier, this won't affect you. Earlier this year, Elastic announced the end of life of Elasticsearch 2.4.6, ending support for the 2.x series, which was introduced in 2015.

At Compose, we're now initiating the process to retire Elasticsearch 2.4.6 from active use. By the end of October 2018, we aim to no longer be provisioning or supporting any Elasticsearch 2.4.6 and to have helped migrate or have migrated all our users to Elasticsearch 5.6.9 or later.

To enable that to happen smoothly, over the month of July, we'll turn off the ability to create new Elasticsearch 2.4.6 for new users. Existing users with Elasticsearch 2.4.6 will, by contacting support, be able to restore deployments or create deployments. All Elasticsearch 2.4.6 users will be contacted by email about this change and have details in that mail to make the support process for provisioning clear and simple.

The simplest way to avoid this issue is to migrate to Elasticsearch 5.6.9. From there you can upgrade to Elasticsearch 6.2, if you want to compress your migration path. Why upgrade (apart from the obvious end of life issue)? If you look back to June last year when we introduced Elasticsearch 5.4.2 to Compose, you'll find a summary. Changes include better indexing, new data structures and a whole new scripting language, Painless, along with numerous enhancements throughout the search engine. One change that doesn't get a mention there is that the "delete by query" plugin goes away, to be replaced by a "delete by query" API.

With Compose, it is easy to restore an existing Elasticsearch backup into a later version of Elasticsearch through the Backup view in the Compose UI. You can run a second upgraded Elasticsearch in parallel with your existing Elasticsearch so you can test and compare performance. Details on this process are included in the Elasticsearch Upgrade and Migrations section of the Compose documentation.

Compose Articles last week

That's it for this week's Noteworthy at Compose. Onwards to next week!

Dj Walker-Morgan
Dj Walker-Morgan is Compose's resident Content Curator, and has been both a developer and writer since Apples came in II flavors and Commodores had Pets. Love this article? Head over to Dj Walker-Morgan’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.