Versions Compared

Old Version 34

changes.mady.by.user Aaron Enfield

Saved on

compared with

New Version 35

changes.mady.by.user Bala Harish A(AC)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

Code Block
languagebash
/usr/share/caringo-elasticsearch-search/bin/configure_elasticsearch_with_swarm_search.py
Warninginfo

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

Note

Warning

The configure script currently requires node.name to be set in /etc/elasticsearch/elasticsearch.yml. This is not the case with an SCI-installed VM; remove the setting and set it to the default value of ${HOSTNAME}.

  1. Compare the backup file to the newly created elasticsearch.yml and add back any customizations needed, such as node.attr.rack and systemctl restart elasticsearch if the configuration was modified.

...

  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. 

    Info
    titleImportant

    Disabling shard allocation or sync-flush can fail to contact the node, but do not proceed to upgrade the next node until the cluster health is green again.

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

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

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

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

  9. 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.