Skip to content

Inconsistent INFO keysizes response #3616

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

Closed
itayTziv opened this issue Apr 24, 2025 · 5 comments
Closed

Inconsistent INFO keysizes response #3616

itayTziv opened this issue Apr 24, 2025 · 5 comments

Comments

@itayTziv
Copy link

When we execute INFO keysizes we sometimes receive dictionary representation (e.g. {'db0_distrib_sets_items': {'1': 1, '2': 1}}) and sometimes string (e.g. {'db0_distrib_sets_items': '1=1'})
The pattern seem to depend on rather it has single element on multiple

@petyaslavova
Copy link
Collaborator

Hi @itayTziv , thank you for pointing this out! We'll have a look at this.

@petyaslavova
Copy link
Collaborator

Hi @itayTziv, can you please share more info about the client(redis-py lib version, sync/async client, cluster/sentinel/standalone) you are using and the Redis database setup you have.
I can't find this property returned by the info command, neither using Redis OSS nor with Redis Enterprise...

@itayTziv
Copy link
Author

This feature should exist in Redis OSS >=7.4 (I'd suggest testing it with Redis 8, it had some bug fixes)
redis-py lib version == 5.2.1

@petyaslavova
Copy link
Collaborator

Hi @itayTziv, I just tested that with the code in master (against latest Redis 8), and the output is as expected, even with just one element: {'db0_distrib_strings_sizes': {'1': 4}, 'db0_distrib_sets_items': {'2': 1}, 'db0_distrib_hashes_items': {'1': 1}}

Also tested with 5.2.1 - sync and async client - the results are still ok.

Do you have a small code example with which I can try to reproduce it locally?

@itayTziv
Copy link
Author

After double checking, we use 2.10.6 version (which is unsuported). can close

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