This article talks about solutions for issues caused by incorrect Elasticsearch (ES) installation and configuration.
On Adobe Commerce on cloud infrastructure please note that service upgrades cannot be pushed to the Production environment without 48 business hours’ notice to our infrastructure team. This is required as we need to ensure that we have an infrastructure support engineer available to update your configuration within a desired timeframe with minimal downtime to your production environment. So 48 hours prior to when your changes need to be on production, submit a support ticket detailing your required service upgrade and stating the time when you want the upgrade process to start.
The following symptoms indicate Elasticsearch is not configured correctly:
Error: No alive nodes in your cluster - this error can appear in Adobe Commerce logs:
Errors indicating that the Elasticsearch version is not compatible with your current version of Adobe Commerce (this is an Adobe Commerce on cloud infrastructure specific error):
[YYYY-MM-DD HH:MM:SS] CRITICAL: Fix configuration with given suggestions: - Elasticsearch version #<version> is not compatible with current version of magento Upgrade elasticsearch version to ~5.0
Where version is the Elasticsearch Service running on the cloud environment.
Elasticsearch is not installed properly. This could be due to:
To correctly set up Elasticsearch:
After you have set up Elasticsearch, check that it’s configured correctly:
curl -XGET <Elasticsearch hostname>:<Elasticsearch server port>For example, in Adobe Commerce on cloud infrastructure:
curl -XGET localhost:9200
php bin/magento config:show catalog/search
catalog/search/engineand ensure it matches with the Elasticsearch version number. For example, in Adobe Commerce on cloud infrastructure:
index_prefix. If you have several environments, make sure you have different
index_prefixvalues for them.