MySQL catalog search engine will be removed in Adobe Commerce 2.4.0. You must have Elasticsearch host setup and configured prior to installing version 2.4.0. Refer to Install and configure Elasticsearch.
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.
This article discusses a fix for problems during deployment after upgrading to Adobe Commerce on cloud infrastructure versions 2.3.1+, if you are on Elasticsearch versions 2.x and 5.x.
Merchants that have upgraded to Adobe Commerce on cloud infrastructure (versions 2.3.1 and onwards) and are on a version of Elasticsearch prior to 6.x can experience errors when deploying. This is because Elasticsearch versions 2.x and 5.x are End of Life and are no longer supported in Adobe Commerce. The Elasticsearch client has to be up to date, or running a deployment risks triggering an error. To learn more, refer to Change the Elasticsearch client in our developer documentation.
When deploying you see an error message similar to the following, indicating that your Elasticsearch version is not compatible: Elasticsearch service version 5.2.2 on infrastructure layer is not compatible with current version of elasticsearch/elasticsearch module (184.108.40.206), used by your Magento application. You can fix this issue by upgrading the Elasticsearch service on your Magento Cloud infrastructure to version 6.x. Other symptoms of this issue may be missing images and problems with filters in your environment.
If you have a shared environment, ensure staging and production are ready to be upgraded.
To solve this issue, the Elasticsearch client module and Elasticsearch service need to be on the latest recommended versions: