Upgrading external Elasticsearch clusters to Elasticsearch 8
In this release of Process Federation Server, using an external Elasticsearch 6.x cluster is no longer supported and using an external Elasticsearch 7.x cluster is deprecated. Instead, you must set up an external Elasticsearch 8.x cluster (see Elasticsearch product end of life dates at https://www.elastic.co/support/eol).
The migration
from
Elasticsearch 6 to Elasticsearch
8
clusters brings in two major changes:
- There no longer is a document type for the documents stored by Process Federation Server in Elasticsearch indices (as a result of the mapping types removal in Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/8.4/removal-of-types.html)
- As index names starting with "." are deprecated in Elasticsearch 8 (see https://www.elastic.co/guide/en/elasticsearch/reference/8.4/indices-create-index.html), when a federated system is declared with an index name of myIndexName, the created index has the name @myIndexName. In Elasticsearch 6, an index named .myIndexName was created with an alias of myIndexName.
If you migrate to Process Federation Server 22.0.2 from an existing topology based on an Elasticsearch 6.x cluster for indexing, you must either rebuild your federated systems indexes from scratch, or migrate your existing Elasticsearch 6.x indices to Elasticsearch 8.x.
If you migrate from an existing topology based on an Elasticsearch 7.x cluster for indexing, the
indices are compatible:
- From Elasticsearch 7.17.0, you can directly upgrade to Elasticsearch 8
- From a version of Elasticsearch lower that 7.17.0, you must first upgrade your cluster to Elasticsearch 7.17 and then to Elasticsearch 8