magento2: Magento2 don't work with redis in cluster mode
Preconditions (*)
- Magento 2.4.3
- Redis 6 configured in cluster mode (or use AWS ElastiCache in cluster mode with 3 masters)
Steps to reproduce (*)
- Run magento
- Configure redis config and cache (redis is configured in cluster mode)
Expected result (*)
- All
./bin/magento
comands works correct and return status code0
- Cache in redis works
Actual result (*)
magento
command returns status code1
with error text, exampleMOVED 2482 122[IP:PORT]
- Cache don’t work
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
- 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”.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 15 (5 by maintainers)
As on the way it’s implemented right now, it causes an issue to integrate with redis, a system requirement to run the application on production with good performance. With that said, why this issue would not be related to Magento core code?
Hi @engcom-Hotel , Earlier you were able to reproduce this issue, https://github.com/magento/magento2/issues/35140#issuecomment-1060242326 but in your latest comment https://github.com/magento/magento2/issues/35140#issuecomment-1343940398 you said it is fixed. Can we know what changes you made to fix this, is there any PR ? Thanks!
Hello,
The related issue has been fixed now and is unable to reproduce on the latest development branch i.e. 2.4-develop. Hence closing this ticket.
Thanks
Hello @ByJacob,
Thanks for the confirmation!
We have tried to reproduce the issue by following the Redis cluster documentation here. And after setting up the Redis cache by following the Magento docs, we are able to reproduce the issue in the latest Magento 2.4-develop branch.
Please have a look at the below screenshot for reference:
Hence confirming this issue.
Thanks
this page explain everything
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Replication.Redis-RedisCluster.html
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/GettingStarted.ConnectToCacheNode.html