Closed Nowi5 closed 4 years ago
Hi @Nowi5, thanks for writing in about this issue. This would almost certainly be an issue with Predis and AWS not being compatible with each other. This package just provides a functional layer on top of Laravel's caching mechanism. I would file a bug with Predis with a complete StackTrace and go from there. Please do keep me informed of your developments, in case I need to make any updates here. Best of luck!
I have the same issues when using my local docker including redis. Let see if the Laravel Community can help: https://github.com/laravel/framework/issues/33733
@Nowi5 Awesome, looks like you got all bases covered. I subscribed to your two other tickets and will follow along to see what comes of it. :)
@mikebronner Thank you for your support as always. Found a temporary solution back from 2017. Do you have any deeper insights to judge if that change makes actually sense? Thank you for your expert opinion.
@Nowi5 My recommendation would be to switch to PHPREDIS, as that is the recommended path forward by Laravel, I believe.
I'm going to work on a release that removes the predis dependency.
@Nowi5 Please give release 0.10.0 a try with PHPRedis and let me know how it goes.
Describe the bug Expected: Clearing the cache across the packages of Laravel (Symfony) and Predis should work with AWS Redis Cluster.
Eloquent Query Please provide the complete eloquent query that caused the bug, for example:
Stack Trace The full stack trace from your log file.
Environment
Additional context have the same issue local and on AWS. Config database.php
Using a AWS Redis Cluster with 3 nodes. Any idea where to start to debug?