NOTE: ElasticSuite and its affiliated applications are third-party tools not currently supported by Adobe. This content is being presented as informational only and not as an indication of what is enabled for Support coverage.
This article talks about the issue of Elasticsearch memory problems caused by tracking indices produced by the ElasticSuite plugin.
Affected products and versions
It is not confirmed what versions of ElasticSuite have this issue.
If the ElasticSuite third-party plugin is installed, you might experience Elasticsearch memory issues, and the Elasticsearch service might crash caused by ElasticSuite tracking indices. Symptoms include:
- Elasticsearch crashes with no memory errors.
- When running a health command
curl -m1 localhost:9200/_cluster/health?prettyor
curl -m1 elasticsearch.internal:9200/_cluster/health?pretty(for starter accounts) there are hundreds or thousands of
- Elasticsearch or site performance is severely degraded.
- "No alive nodes found in your cluster" in Elasticsearch deploy or log errors.
- "Rejecting mapping update to [<*>tracking_log_event<*>]" in deploy or log errors.
ElasticSuite has a new feature that creates tracking indices. These tracking indices record which search terms are the most used, which terms generate the most turnover, and which terms are leading to a no results page so merchants can create synonyms to fix them. It does not appear to delete the tracking indices, so Elasticsearch runs out of resources and crashes.
Create a cron job to delete the tracking indices. This command deletes indices created in the last month:
curl -XDELETE localhost:9200/<name in index> * **\_tracking\_log** * _$(date +'%Y%m' -d 'last month')*
If you want to delete indices at a set time-frequency, create a cron job by referring to the following articles in our developer documentation: