What should be the next step?

An Architect is investigating a merchant’s Adobe Commerce production environment where all customer session data is randomly being lost. Customer session data has been configured to be persisted using Redis, as are all caches (except full page cache, which is handled via Varnish).

After an initial review, the Architect is able to replicate the loss of customer session data by flushing the Magento cache storage, either via the Adobe Commerce Admin Panel or running bin/iuagento cache: flush on the command line. Refreshing all the caches in the Adobe Commerce Admin Panel or running bin/magento cache: clean on the command line does not cause session data to be lost.

What should be the next step?
A . Educate the merchant to not flush cache storage and only refresh the caches in future.
B. Set the ‘Stores > Configuration’ option for "Store Session Data Separately’ to ‘Yes’ in the Adobe Commerce Admin Panel.
C. Check app/etc/evn.php and make sure that the Redis configuration for caches and session data use different database numbers.

View Answer

Answer: C

Explanation:

This is because when the Magento cache storage is flushed, all caches and session data stored in Redis are cleared. To prevent session data from being lost when caches are flushed, the merchant should configure different Redis databases for caches and session data, so that flushing the Magento cache storage only clears the caches and not the session data.