Tracking turned off, tracking indices still being created

[Thertor]

Preconditions

Magento Version : Magento 2.3.1 Communitry Edition and Magento 2.3.2 Enterprise

ElasticSuite Version : 2.8.2

Environment : Production mode

Elasticsearch: 6.8+

Steps to reproduce

1. Setup elasticsuite
2. Set tracking in the module to false
3. Let people do search etc
4. Tracking indices are still created and updated

Expected result

1. Tracking indices shouldn't be created and update

Actual result

1. Tracking indices are created and updated

This has happened with several of our M2 customers now, on different versions of Magento, the two best examples are both running the same elasticsuite version.

[rbayet]

Hello @Thertor,

Strange, this looks like #1252 (fixed in 2.6.6 and 2.7.4) is back ...
Are you sure that events dating from after the tracking is disabled end up in new Elasticsearch indices ?
This could be previous events clogging the DB storage table.

Regards,

[Thertor]

Yes, the tracking was never enabled in the first place before I added these two to the ES cluster.

[rbayet]

Hello @Thertor,

Sorry, I cannot reproduce your issue in 2.8.2 or 2.8.4.
Once disabled, the tracker does not collect any new event, ie no new record is added to table elasticsuite_tracker_log_event.

On the other hand, as stated, if you still had some events dating from right before disabling the tracker in Stores > Configuration > Elasticsuite > Tracking, then any cron:run execution will indeed index those remaining events in the Elasticsearch server.
Hence my remark about

This could be previous events clogging the DB storage table.

We could probably decide not to index them at all and let them be in the storage DB table.

Something that bothers me, you say

Yes, the tracking was never enabled in the first place before I added these two to the ES cluster.

The tracking is enabled by default when installing the module, so it does not need to be explicitly enabled.
Were you saying that you had taken extra steps to make sure the tracking was disabled before deploying ?

Regards,

[no-response]

This issue was waiting update from the author for too long.
Without any update, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.