Open deanrad opened 9 years ago
We've determined the cause of this issue--- AWS elasticache disallows the use of the CONFIG Redis command.
Even if you've configured keyspace notification properly it appears that by just calling connection.config('get', ...)
. I propose an extra setting SKIP_CONFIG_CHECK
or something along those lines as it will allow users who have already set up redis properly to still connect. If SKIP_CONFIG_CHECK
is set to true/1 log a warning saying so.
We have an app which works against a manually installed Redis, but when we point it to Elasticache in AWS we get:
Any insight to what this error means ? Has this package been tested against elasticache ?
Reproduction steps: