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

[redis] upstash shows error when accessing too many keys #418

Open
1 task
Rigo-m opened this issue Mar 27, 2024 · 3 comments
Open
1 task

[redis] upstash shows error when accessing too many keys #418

Rigo-m opened this issue Mar 27, 2024 · 3 comments

Comments

@Rigo-m
Copy link

Rigo-m commented Mar 27, 2024

Describe the feature

Working with large redis db, you might encounter an error if you try to fetch too many keys altogether.
There should be a scan option available (or getKeys should be implemented via scan)

Additional information

  • Would you be willing to help implement this feature?
@pi0
Copy link
Member

pi0 commented Mar 28, 2024

Would you please share runnable reproduction?

@Rigo-m
Copy link
Author

Rigo-m commented Mar 28, 2024

Hi pi0, using upstash as a redis provider
https://stackblitz.com/edit/nuxt-starter-ako5kk?file=server%2Fapi%2Ferror-redis.ts this simple script triggers the error when using getKeys.

Actually, as a second thought, I'm not sure whether the error is from upstash which is prohibiting reading that many keys altogether (since it is a blocking operation https://redis.io/commands/keys/) or whether it is a redis limitation.
Can I do anything else?

@pi0 pi0 changed the title Missing Scan feature for keys in redis driver [redis] upstash shows error when accessing too many keys May 1, 2024
@pi0
Copy link
Member

pi0 commented May 1, 2024

Hi @chronark do you know if it is a known limitation? And what would you suggest to scan too many keys?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants