MySQL catalog search engine will be removed in Adobe Commerce 2.4.0. You must have the Elasticsearch host set up and configured prior to installing version 2.4.1. Refer to Install and configure Elasticsearch.
This article discusses that it is a recommended best practice to replace the default MySQL search engine in Adobe Commerce with Elasticsearch because Elasticsearch is a better-performing search engine.
Affected Products and Versions:
- Adobe Commerce 2.x.x
The MySQL search engine has a slower performance compared to using Elasticsearch.
In large applications of Adobe Commerce, the MySQL data cache stored in RAM can grow very large and be subjected to thousands or millions of requests per second.
MySQL does not have a strong memory-focused search engine. MySQL search has a relatively high overhead and cannot deliver optimal speed. Because MySQL search is not designed for very high concurrency, users can be exposed to bottlenecks and periodic negative performance impacts that can result in slow user experiences.
Configure and enable the Elasticsearch engine as described in Configure Adobe Commerce to use Elasticsearch.
- Set up Elasticsearch service in our developer documentation.
- Install and configure Elasticsearch in our developer documentation.
- MySQL and ElasticSearch search engines show different results in the same conditions in our support knowledge base.
- Ensure Elasticsearch is installed properly in our support knowledge base.
- Elasticsearch: Getting Started in .elastic.co.