This article is a troubleshooter tool for Adobe Commerce on-premises and Adobe Commerce on cloud infrastructure merchants 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.
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.
$ redis-cli -p 6370 info | grep redis_version// Pro or Staging
$ redis-cli -h 'redis.internal' info | grep redis_version// Starter or Integration
a. YES – Proceed to Step 4.
b. NO – Adobe Commerce supports Redis versions 3.2 and 5.0. If you are running Adobe Commerce on cloud infrastructure 2.3.3 or higher, we recommend upgrading to Redis 5. For setup steps on Adobe Commerce on cloud infrastructure Pro plan architecture, Integration and Starter environments including the master branch, refer to Adobe Commerce on cloud infrastructure > Set up Redis service in our developer documentation. Note:You must submit a support ticket to change the service configuration on Pro architecture Production and Staging environments. Also, for Adobe Commerce on cloud infrastructure and Adobe Commerce on-premises 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 Adobe Commerce request. For steps, refer to Extended Redis cache implementation Adobe Commerce 2.3.5+ in our support knowledge base. For all other Adobe Commerce users, refer to Adobe Commerce Configuration Guide > Configure Redis in our developer documentation, for steps.
$php vendor/bin/composer info magento/ece-tools
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.
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.