Upgrading Elasticsearch

This is the process for in-place upgrades of Elasticsearch (ES), using an existing Search feed and index data.


Upgrading Elasticsearch by Script

On each node in an Elasticsearch cluster, follow this process and run the files from the Swarm download bundle:

  1. Before upgrading, query the Elasticsearch cluster for the list of nodes.

    curl -i http://ELASTICSEARCH:9200/_cat/nodes

    Example output:
    [root@elasticsearch Elasticsearch]# curl -i http://<ip-address>:9200/_cat/nodes
    HTTP/1.1 200 OK
    content-type: text/plain; charset=UTF-8
    content-length: 300

    <ip-node1> 14 99 1 0.02 0.14 0.15 dilm - <hostname-node1>
    <ip-node2>  1 71 1 0.01 0.09 0.08 dilm - <hostname-node2>
    <ip-node3> 72 99 0 0.08 0.06 0.08 dilm - <hostname-node3>
    <ip-node4> 50 99 0 0.03 0.04 0.05 dilm * <hostname-node4>
    <ip-node5> 47 99 1 0.08 0.14 0.22 dilm - <hostname-node5>

    The node with the * is the Elasticsearch master node. It is recommended to upgrade the node last to avoid problems electing a new master node.

  2. Backup the existing configurations so a record exists of any customizations. Run ./techsupport-bundle-grab.sh from your Support tools directory to do this, making sure to upgrade your support tools prior to running the script. Instructions are here.

  3. Start by installing the latest Swarm Search, which is the caringo-elasticsearch-search RPM.

    yum install caringo-elasticsearch-search-VERSION.noarch.rpm


The error: "ES_PATH_CONF must be set to the configuration path chown: cannot access '/etc/elasticsearch/elasticsearch.keystore': No such file or directory" displays if Elasticsearch 7 RPM was inadvertently installed. Install the caringo-elasticsearch-search RPM to proceed.

  1. Run the script that installs and configures the upgrade.
    If the script detects that Elasticsearch is installed and configured, it runs with --upgrade instead of configuring a new cluster, automating the Elasticsearch rolling upgrade steps (https://www.elastic.co/guide/en/elasticsearch/reference/7.17/rolling-upgrades.html).



The upgrade requires Internet access to download the Elasticsearch rpm. Place elasticsearch-7.17.*.rpm in the current directory if Internet access is unavailable.

  1. Compare the backup file to the newly created elasticsearch.yml and add back any customizations needed and systemctl restart elasticsearch if the configuration was modified.

  1. Verify that all nodes are accounted for, all shards are assigned, and the status is green.

The script updates the configuration files and restarts the service if Elasticsearch 7 is already installed.

Upgrading Elasticsearch Manually

These are the steps the script automates if you need to upgrade manually:

  1. It fixes /etc/sysconfig/elasticsearch to the correct ES6 version (the same as ES7).

  2. It increases the systemd timeout in /etc/systemd/system/elasticsearch.service.d/override.conf (see github.com/elastic/elasticsearch/issues/60140)

  3. A prompt to continue with the yum upgrade to 7.5.2 appears after refreshing the config files for Elasticsearch 6.

  4. It disables shard allocation and does a POST synced-flush for safer rolling upgrades. 

  1. It uninstalls the Prometheus Exporter plugin if it exists.

  2. It shells out to yum to install the Elasticsearch 7 RPM in the current directory or from artifacts.elastic.co, if unavailable.

  3. It updates elasticsearch.yml for version 7 compatibility, including discovery.initial_master_nodes instead of discovery.zen.unicast.hosts, and jvm.options.

  4. It starts the upgraded Elasticsearch 7 and waits for it to be ready.

  5. The cluster re-enables shard allocation and prompts to repeat these two steps on the next node if the cluster health is green or yellow.

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.