Cause

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.

Solution

Upgrade your ElasticSuite version to be able to cleanup tracking indices periodically

Once you have upgraded the ElasticSuite plugin to version higher than 2.8.0, you can configure a periodical cleaning of indices.

Go to Stores > Configuration > Tracking > Global Configuration > Retention Delay

The default retention period is 365 days. You can reduce it to 30 or 15 days.

Upgrade your ElasticSuite version to use monthly based indices instead of daily based indices

Once you have upgraded the ElasticSuite plugin to version > 2.9.8 / 2.10.7, tracking indices will be monthly based.

You can still reduce the retention period :

Go to Stores > Configuration > Tracking > Global Configuration > Retention Delay

The default retention period is 12 months (will generate 12 indices). You can reduce it to 3 or 6 months.

Use a cronjob to cleanup tracking indices data

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:

Previous pageElasticsearch issues after Adobe Commerce cloud infrastructure 2.3.1+ upgrade
Next pageEnsure Elasticsearch is installed properly

Commerce


Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more