Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[6.x] Fixes the issue using cache:clear with PhpRedis and a clustered Redis instance. #36665

Conversation

J5Dev
Copy link
Contributor

@J5Dev J5Dev commented Mar 19, 2021

This is simply a replication of the fix by @willbrowningme in MR #36281 which was already merged to the 8.x release branch.

The issue is however still unfixed within the 6.x LTS release, so this PR is a simple replication of the work previously undertaken to allow for the fix to be merged into the 6.x branch.

I have tested that as with the other branch, these changes not only work, but also have no adverse affects. In addition to replicating the tests undertaken by @willbrowningme I have also tested this within a Kubernetes environment running both php-fpm 7.3 & 7.4 tests alongside a clustered Redis instance.

…Redis instance, by updating the PhpRedisConnection flushdb method to use the already open/configured clients.
@J5Dev J5Dev changed the title Fixes the issue using cache:clear with PhpRedis and a clustered Redis instance. [6.X] Fixes the issue using cache:clear with PhpRedis and a clustered Redis instance. Mar 19, 2021
@driesvints driesvints changed the title [6.X] Fixes the issue using cache:clear with PhpRedis and a clustered Redis instance. [6.x] Fixes the issue using cache:clear with PhpRedis and a clustered Redis instance. Mar 19, 2021
@taylorotwell taylorotwell merged commit 1ac5370 into laravel:6.x Mar 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants