This article provides a fix for the issue when logging in to the Commerce Admin or opening the checkout page causes lag or timeout (over 30 seconds). The issue occurs when Redis is used for session storage.
Cause: Github issue #12385.
Solution: update to the latest Adobe Commerce patch to fix these issues for all versions of Redis and specific versions of Adobe Commerce.
If you use Adobe Commerce on cloud infrastructure version 2.2.0, a workaround is available.
Logging in to the Commerce Admin or proceeding to the checkout page takes over 30 seconds.
This only occurs when user sessions are stored in Redis.
Adobe Commerce had an issue with the session locking mechanism that added a 30-seconds timeout to some operations when Redis was used for session storage. For details, see the Github issue #12385.
This issue has been fixed in Adobe Commerce 2.1.14 and 2.2.2.
To receive a patch, submit a support ticket requesting the patch. In your ticket, specify your Adobe Commerce version and the corresponding reference number for the patch:
The general (version-agnostic) reference number is MAGETWO-84289.
If you have previously considered upgrading to Adobe Commerce 2.2.2 or later, you may use this update opportunity to fix the issue.
To disable session locking, set
1 in the Redis configuration section of the
'session' => array ( 'save' => 'redis', 'redis' => array ( 'host' => 'redis.internal', 'port' => 6379, 'database' => '0', 'disable_locking' => '1' ), ),
This solution does not affect any other Adobe Commerce functionality.
After applying the patch with the fix, the workaround is not required anymore, so you may revert it (set
The ECE-Tools deployment script package with versions 2002.0.3 - 2002.0.7 applies the workaround automatically, setting
1. This disables the session locking mechanism for Adobe Commerce 2.2.0, on which the original issue does not occur.
If you are running Adobe Commerce on cloud infrastructure 2.2.0, upgrade ECE-Tools to v2002.0.8 of later. You may also consider upgrading your Adobe Commerce on cloud infrastructure to 2.2.2 or later.