-
Notifications
You must be signed in to change notification settings - Fork 197
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
Serverless AWS Redis results in redis.exceptions.ResponseError: Lua scripts without any input keys are not supported.
#379
Comments
Grrr. There's not going to be anything we can do about this. The PubSub channel layer doesn't use Lua so you could try that. |
I'm using the ServerLess Redis Cache from ElastiCache AWS and getting the error. Exception inside application: Lua scripts without any input keys are not supported. Here is the config:
.env redis host: REDIS_HOST=rediss://<>.serverless.euw2.cache.amazonaws.com:6379 |
For posterity: Confirming I can bypass the Lua issues for Serverless caches (and replication groups) using the pubsub channel layer. (Confirmed on valkey and redis). Note: on single instances in aws, the endpoints support Also worth noting: Not all redis features are supported on serverless caches. Like: Some of this is noted in the AWS docs here: https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/SupportedCommands.html#RestrictedCommandsRedis I was not able to find other AWS docs on non supported items like Lua (which are supported in single instances but not multi) and directly relevant to this thread. Some other functions (similar to get_many) that appear to be supported are not quite there yet. The basics seem to work well (get, set, delete ...), so you may just have to write loops for get_many and set_many. Methods like Anyway, here is my connection code. Hope it can help.
Special shout out / thanks to: @carltongibson for the great pointer. |
Works on "design your own cache" redis clusters but not serverless (engine version 7.1 for both).
Running daphne in docker on aws ec2.
Traceback:
Pip freeze:
The text was updated successfully, but these errors were encountered: