Elasticsearch Upgrade

Elasticsearch Upgrade

Opster Team

Nov 2020


In addition to reading this guide, run the Elasticsearch Health Check-Up. Detect problems and improve performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and many more.
Free tool that requires no installation with +1000 users.

Run the Elasticsearch check-up to receive recommendations like this:

checklist Run Check-Up
error

The following configuration error was detected on node 123...

error-img

Description

This error can have a severe impact on your system. It's important to understand that it was caused by...

error-img

Recommendation

In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...

1

X-PUT curl -H "Content-Type: application/json" [customized recommendation]

Overview

Upgrade refers to migrating your Elasticsearch version to a newer version. An upgrade of an existing cluster can be done in two ways: through a rolling upgrade and through a full cluster restart. The benefit of a rolling upgrade is having zero downtime.

Common problems and important points

  • The major problem with upgrades is version incompatibility. Elasticsearch supports rolling upgrades only between minor versions. You need to make sure to go through the official documentation to see if your cluster can support a rolling upgrade, otherwise a complete reindexing is required.
  • Once you upgrade an Elasticsearch node, a rollback can not be done. You need to make sure to take data backups before an upgrade.
  • Elasticsearch continuously removes or deprecates some of its features with every release, so keep an eye on the change logs of each version before planning an upgrade. 
  • While doing a rolling upgrade, it is important to disable shard allocation before stopping a node and enable the shard allocation when node is upgraded and restarted. This process helps in avoiding unnecessary IO load in the cluster.

Run the Elasticsearch check-up to receive recommendations like this:

checklist Run Check-Up
error

The following configuration error was detected on node 123...

error-img

Description

This error can have a severe impact on your system. It's important to understand that it was caused by...

error-img

Recommendation

In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...

1

X-PUT curl -H "Content-Type: application/json" [customized recommendation]


Related log errors to this ES concept


Starting segment upgrade upgradeOnlyAncientSegments=
Templates are still reported as out of date after the upgrade. The template upgrade will be retried.
Templates were upgraded successfully to version
Not updating settings for the index because upgraded of some primary shards failed
Error occurred while reindexing
Error occurred while upgrading index
Isolating datafeeds:
Not starting watcher; upgrade API run required: .watches; .triggeredwatches
Finished segment upgrade
Error occurred while reindexing; bulk failures ; search failures
Error updating template ; request was not acknowledged
Templates were partially upgraded to version

< Page: 1 of 3 >




Improve Elasticsearch Performance

Run The Analysis