This article is a troubleshooter tool for Magento Commerce and Magento Commerce Cloud customers having issues with Redis. Click on each question to reveal the answer in each step of the troubleshooter. Depending on your symptoms and configuration, the troubleshooter will explain how to troubleshoot version and memory issues and optimize performance.
Step 1
a. YES – Proceed to Step 2.
b. NO – Return to support.magento.com and search for relevant troubleshooting articles.
Step 2
a. YES – Proceed to Step 3.
b. NO – Make sure you have the latest version of the package magento-cloud-patches installed. This package has the necessary patches for Redis. To access go to GitHub magneto-cloud-patches.
Step 3
Check by running the following command in the CLI:
$ redis-cli -p 6370 info | grep redis_version // Pro or Staging$ redis-cli -h 'redis.internal' info | grep redis_version // Starter or Integrationa. YES – Proceed to Step 4.
b. NO – Magento supports Redis versions 3 .2 and 5.0. If you are running Magento Commerce Cloud 2.3.3 or higher, we recommend upgrading to Redis 5. For setup steps on Magento Commerce Cloud Pro, Integration and Starter environments including the master branch, refer to DevDocs Magento Commerce Cloud > Set up Redis service. Note: You must submit a support ticket to change the service configuration on Pro Production and Staging environments. Also, for Magento Commerce Cloud and Magento Commerce 2.3.5+, extended Redis cache implementation is recommended. This type of Redis cache implementation provides enhancements that minimize the number of queries to Redis that are performed on each Magento request. For steps, refer to Extended Redis cache implementation Magento Commerce Cloud and Cloud 2.3.5+.
For all other Magento Commerce users, refer to DevDocs Magento Configuration Guide > Configure Redis, for steps.
Step 4
$php vendor/bin/composer info magento/ece-toolsa. YES – Proceed to Step 5.
b. NO – Upgrade ECE-Tools to the latest release.
Step 5
a. YES – Try the following: For a non-split architecture, make sure a secondary connection is used. For split architecture, the L2 cache must be enabled.
b. NO – Configure L2 cache configuration by Updating Redis Backend. Proceed to Step 6.
Step 6
a. YES – Check the temp directory /dev/shm to see if you need to increase space. If you need more space, submit a support ticket.
b. NO – Enabling L2 cache appears to have solved your Redis issues.