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 eval error: ERR unknown subcommand 'setinfo'. Try CLIENT HELP. #2910

Closed
gwkline opened this issue Feb 18, 2024 · 3 comments · Fixed by #2915
Closed

redis eval error: ERR unknown subcommand 'setinfo'. Try CLIENT HELP. #2910

gwkline opened this issue Feb 18, 2024 · 3 comments · Fixed by #2915

Comments

@gwkline
Copy link

gwkline commented Feb 18, 2024

Running into this error since updating from 9.4.0 to 9.5.0:

redis eval error: ERR unknown subcommand 'setinfo'. Try CLIENT HELP.

Not sure if this is an issue with how our worker queue package is interfacing with redis, but since the recent release made changes to setinfo I figured I would raise the issue just in case. I will try and update this issue with pertinent info as I investigate further

Running on go 1.22.0, the worker queue package is called asynq. Thanks!

@ofekshenawa
Copy link
Collaborator

Hey @gwkline ,

The client setinfo command has been available since Redis version 7.2.0. This command is automatically run at the start of each connection. If you wish to prevent this from happening, you can modify your connection options to include DisableIdentity: true . This will stop the command from executing at the beginning of each connection.

Please let us know if this solution addresses your issue or if you need any further assistance:)

@mayah
Copy link

mayah commented Feb 19, 2024

Hi, I encountered the same problem. DisableIndentity: true solved the issue.

By the way, isn't this option a typo?
DisableIdentity (not I*n*dentity) seems correct to me.
(It's already pointed out in #2708 (comment), though)

@ofekshenawa ofekshenawa linked a pull request Feb 19, 2024 that will close this issue
@gwkline
Copy link
Author

gwkline commented Feb 19, 2024

Hey @gwkline ,

The client setinfo command has been available since Redis version 7.2.0. This command is automatically run at the start of each connection. If you wish to prevent this from happening, you can modify your connection options to include DisableIdentity: true . This will stop the command from executing at the beginning of each connection.

Please let us know if this solution addresses your issue or if you need any further assistance:)

This was the issue, Heroku defaults to using Redis 7.0 currently, upgrading to 7.2 fixed! Thanks for the help.

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.

3 participants