Skip to content
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

Elasticache cluster - CROSSLOT Keys in request don't hash to the same slot #7802

Closed
chandank-nu opened this issue Dec 13, 2023 · 4 comments
Closed

Comments

@chandank-nu
Copy link

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

@robertzlatarski
Copy link

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?

@robertzlatarski
Copy link

I have found the problem: using KeyvRedis without specifying useRedisSets: false.

@glasser
Copy link
Member

glasser commented Jan 5, 2024

Yeah, looks like @keyv/redis added a new feature in a minor version that arguably changed semantics enough that it should have been a major version bump... https://github.com/jaredwray/keyv/releases/tag/2023-07-01

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?

@glasser glasser closed this as not planned Won't fix, can't repro, duplicate, stale Jan 5, 2024
Copy link
Contributor

github-actions bot commented Feb 5, 2024

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants