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

Increase REDIS key size more than 512 MB #7354

Closed
boseabhishek opened this issue Jun 2, 2020 · 4 comments · Fixed by #4633
Closed

Increase REDIS key size more than 512 MB #7354

boseabhishek opened this issue Jun 2, 2020 · 4 comments · Fixed by #4633

Comments

@boseabhishek
Copy link

Hello All,

I am pretty new to REDIS. As per the official documentation(https://redis.io/topics/data-types-intro#redis-keys), we see that:
 - The maximum allowed key size is 512 MB.

I have seen some discussion around increasing the limit but didn't quite understand if we had a definite answer.

@kpbird
Copy link

kpbird commented Jun 4, 2020

Hello,

512 MB key size is more than sufficient. Do you have any specific use case where you need a key size more than 512 MB?

@soloestoy
Copy link
Collaborator

Hi, this is already supported since 5.0 using configuration proto-max-bulk-len, see more details in redis.conf

@oranagra
Copy link
Member

@soloestoy i don't think that's right (yet?).
proto-max-bulk-len allows bigger protocol bulks, but that's mainly helping big RESTORE commands (ones carrying a huge hash or list).

it does indeed enables you to create big strings with SET / HSET, but there are some places with extra checks like SETRANGE and APPEND that use this:

static int checkStringLength(client *c, long long size) {
    if (size > 512*1024*1024) {

@soloestoy
Copy link
Collaborator

@oranagra sorry I missed it, seems we need to add a new configuration.

BTW, this remind me about #4633

@soloestoy soloestoy reopened this Aug 11, 2020
@oranagra oranagra linked a pull request Aug 11, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants