- Newest
- Most votes
- Most comments
ElastiCache Serverless has a maximum limit of 4000 arguments per request. Crossing this limit can trigger "Connection reset by peer" errors on the Redis client. This is also addressed in our docs. Check if this is what is happening in your case.
Key name length - 4 KiB (The maximum size for a single Redis key or channel name. Clients referencing keys larger than this will receive an error.)
Additionally, I would like to clarify whether it's necessary to enable cluster mode in Predis to effectively use ElastiCache Serverless for Redis, even though my application is not explicitly configured to use Redis in cluster mode.
Yes, even though the proxy layer implementation in Serverless makes it look like your application is talking to a single endpoint, the client is still expected to be cluster-aware. For example all the keys in a multi-key operation are expected to be in the same hash slot, if not you will hit the same CROSSSLOT error seen in Cluster Mode Enabled clusters.
Relevant content
- asked 19 days ago
- asked 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 8 months ago