You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using AWS elasticache cluster redis for GQL response caching which was working fine with V3 server but after migrating to V4 we started getting error "CROSSLOT Keys in request don't hash to the same slot"
Link to Reproduction
N/A
Reproduction Steps
No response
The text was updated successfully, but these errors were encountered:
I am getting this error as well: Error writing from RESTDataSource to cache: ReplyError: CROSSSLOT Keys in request don't hash to the same slot. Have you managed to resolve it?
I don't think this really is an Apollo Server bug so I'll close this, but is it possible some of our docs could be improved to help people avoid this issue?
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.
Issue Description
We're using AWS elasticache cluster redis for GQL response caching which was working fine with V3 server but after migrating to V4 we started getting error "CROSSLOT Keys in request don't hash to the same slot"
Link to Reproduction
N/A
Reproduction Steps
No response
The text was updated successfully, but these errors were encountered: