[12.x] Fixing MemoizedStore with Redis Cluster #57828
Merged
+8
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is split from of #57714
MemoizedStoreTest was skipped in #57710, it was failing with RedisCluster, because such commands as FlushAll and FlushDb should be called on each node separately.
Laravel already has implementation for flushDb over all nodes in cluster. So just replacing flushAll with flushing databases used in test to unskip it.
After that test failed on PredisClusterConnection (see https://github.com/laravel/framework/actions/runs/19509599522/job/55845498143)
That's because MemoizedStore relies heavily on
manymethod, that do not work on PredisCluster, if keys hashes to different slots. PHPRedis mget implementation works well even if key hashes differs.So, i replicated solution from #53940 , but only for PredisCluster.