Magento doesn't work with Redis in cluster mode

speller commented 1 month ago

Preconditions and environment

Magento version 2.4.7
ElastiCache Serverless Redis (cluster mode is always on)

Steps to reproduce

Run cache clean command

Expected result

It works properly

Actual result

Error

Error cleaning cache by mode matchingTag: CROSSSLOT Keys in request don't hash to the same slot
#0 /magento/vendor/colinmollenhour/cache-backend-redis/Cm/Cache/Backend/Redis.php(1010): Zend_Cache::throwException('Error cleaning ...', Object(CredisException))
#1 /magento/vendor/magento/zend-cache/library/Zend/Cache/Core.php(465): Cm_Cache_Backend_Redis->clean('matchingTag', Array)\n#2 /magento/vendor/magento/framework/Cache/Core.php(92): Zend_Cache_Core->clean('matchingTag', Array)
#3 /magento/vendor/magento/framework/Cache/Frontend/Adapter/Zend.php(103): Magento\\Framework\\Cache\\Core->clean('matchingTag', Array)\n#4 /magento/vendor/magento/framework/Cache/Frontend/Decorator/Bare.php(89): Magento\\Framework\\Cache\\Frontend\\Adapter\\Zend->clean('matchingTag', Array)
#5 /magento/vendor/magento/framework/Cache/Frontend/Decorator/TagScope.php(76): Magento\\Framework\\Cache\\Frontend\\Decorator\\Bare->clean('matchingTag', Array)
#6 /magento/vendor/magento/framework/Cache/Frontend/Decorator/Bare.php(89): Magento\\Framework\\Cache\\Frontend\\Decorator\\TagScope->clean('matchingTag', Array)
#7 /magento/vendor/magento/framework/Cache/Frontend/Decorator/Logger.php(47): Magento\\Framework\\Cache\\Frontend\\Decorator\\Bare->clean('matchingTag', Array)
#8 /magento/vendor/magento/framework/Cache/Frontend/Decorator/Bare.php(89): Magento\\Framework\\Cache\\Frontend\\Decorator\\Logger->clean('matchingTag', Array)
#9 /magento/vendor/magento/framework/App/Cache/Type/AccessProxy.php(107): Magento\\Framework\\Cache\\Frontend\\Decorator\\Bare->clean('matchingTag', Array)
#10 /magento/vendor/magento/framework/Cache/Frontend/Decorator/Bare.php(89): Magento\\Framework\\App\\Cache\\Type\\AccessProxy->clean('matchingTag', Array)
#11 /magento/vendor/magento/framework/Cache/Frontend/Decorator/TagScope.php(76): Magento\\Framework\\Cache\\Frontend\\Decorator\\Bare->clean('matchingTag', Array)
#12 /magento/vendor/magento/module-page-cache/Model/Cache/Type.php(52): Magento\\Framework\\Cache\\Frontend\\Decorator\\TagScope->clean('matchingTag', Array)
#13 /magento/vendor/magento/module-page-cache/Observer/FlushAllCache.php(66): Magento\\PageCache\\Model\\Cache\\Type->clean()

Additional information

No response

Release note

No response

Triage and priority

[ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 1 month ago

Hi @speller. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

For more details, review the Magento Contributor Assistant documentation.
Add a comment to assign the issue: @magento I am working on this
To learn more about issue processing workflow, refer to the Code Contributions.

Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

hostep commented 1 month ago

I'm not sure this should be reported to Magento, maybe a better place to report it would be to one of the colinmollenhour redis repo's that deal with the communication from Magento to Redis.

I think there are already some (old) attempts at adding that functionality, just posting some links, I'm not familiar with the technology so no idea if these make sense for your request:

speller commented 1 month ago

@hostep the referenced PR suggests adding a new client class and Magento should also add support for it. So some work on the Magento side is also required.

JacobBrownAustin commented 1 month ago

FYI, I'm already working on a pull request for the session part of it of it (not the cache backend). It's a simple PR from the Magento side since it just exposes the new configuration options for clusters to the PR I've made to the php-redis-session-abstract. I'm not working at all on the cache part at all, so I can't comment on that.

m2-assistant[bot] commented 3 weeks ago

Hi @engcom-Hotel. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
[ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-Hotel commented 3 weeks ago

Hello @speller,

Thanks for the report and collaboration!

We have tried to reproduce the issue in the vanilla Magento 2.4-develop branch with Redis in cluster mode. The issue seems reproducible for us.

Hence confirming the issue.

Thanks

github-jira-sync-bot commented 3 weeks ago

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-13291 is successfully created for this GitHub issue.

m2-assistant[bot] commented 3 weeks ago

:white_check_mark: Confirmed by @engcom-Hotel. Thank you for verifying the issue.
Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

devops-digitalsilk commented 5 days ago

We have the same issue with Cluster mode enabled, doesn't even to be serverless.

magento / magento2