Upgrading Elasticsearch to version 9.3.3

01/06/2026

Graph Modeling (formerly PoolParty) now requires Elasticsearch version 9.x or higher to ensure compatibility across all Graphwise components. If you are using an incompatible version, or wish to bypass the automated migration during your upgrade to 10.2, you can use the instructions below to either perform a manual upgrade or run the automated script for Compose deployments.

You can also refer to the original Elasticsearch documentation describing the additional preparation steps when upgrading from version 8.x.

As the upgrade to version 9.3.3 is only possible if you are already using Elasticsearch 8.19.13 or higher the procedure below also lists a step covering an upgrade to version 8.19.x.

Warning

Remember to create a backup of your existing indices before starting any upgrade in order to be able to be able roll back.

Tip

Direct upgrades to Elasticsearch 9.x are supported if you are already running version 8.19.x. If you are upgrading from an earlier version (pre-8.19.x), you must first perform an intermediary upgrade to version 8.19.x before proceeding to 9.x.

For Docker Compose deployments upgrading to Graph Modeling version 10.2, an automated Elasticsearch Upgrade Orchestrator is available in our open-source compose-files repository. Please carefully review the repository's README file for complete instructions and prerequisites before using the tool.

Note

This procedure is only relevant for upgrading of existing environments. If you are intending to have a fresh installation of Graph Modeling 10.2 (formerly PoolParty) as it already uses the 9.3.3 version of Elasticsearch which is included in the compose file for this Graph Modeling version.

Warning

Before you start the upgrade to Elasticsearch 8.19.13 it is essential to create a full backup (snapshot) of your data.

Upgrading Elasticsearch Manually

Change the Elasticsearch image to 8.19.13 (docker-compose.yaml)
Start the deployment
Use docker compose up -d
Wait until Elasticsearch cluster successfully completes re-indexing with no errors and has returned to the the Green health status
Stop the deployment (docker compose down)
Change the Elasticsearch image to 9.3.3 (docker-compose.yaml)
Start the deployment again
Use docker compose up -d
Wait until Graph Modeling (formerly PoolParty) becomes responsive
After successful migration to Elasticsearch 9.3.3 the environment is ready for use with Graph Modeling 10.2 (formerly PoolParty)

In this section: