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

'recommeded to use a minimum Redis version of 6.2.0', orly? #1442

Closed
antirek opened this issue Sep 23, 2022 · 5 comments
Closed

'recommeded to use a minimum Redis version of 6.2.0', orly? #1442

antirek opened this issue Sep 23, 2022 · 5 comments

Comments

@antirek
Copy link

antirek commented Sep 23, 2022

updated to bullmq@2.0.2
received warning message in console

It is highly recommeded to use a minimum Redis version of 6.2.0
           Current: 6.0.8

I use ioredis@5.2.3
also I check package-lock.json that project doesn't have any deps from redis, how it check and find 6.0.8?

@antirek
Copy link
Author

antirek commented Sep 23, 2022

read code again and understand ))

@antirek antirek closed this as completed Sep 23, 2022
@manast
Copy link
Contributor

manast commented Sep 23, 2022

6.0.8 is going to be ok, the issues start with versions lower than 6.0.0.

@0x7357
Copy link

0x7357 commented Oct 11, 2022

@antirek How do you've fixed that issue?

Edit: I see. It's the redis version installed on the server. Would be good to edit the hint. Like: "The Redis version of the connected Redis server should be at least 6.0.0. Please consider updating Redis on your server."

@manast
Copy link
Contributor

manast commented Oct 11, 2022

@0x7357 I am all for making the messages as clear as possible, but which other Redis version could it be other than the one you are connecting to?🤔

@0x7357
Copy link

0x7357 commented Oct 11, 2022

@0x7357 I am all for making the messages as clear as possible, but which other Redis version could it be other than the one you are connecting to?🤔

I have tried everything to keep the client versions up to date. :-D I didn't even think about the server because I assumed it was up to date.

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

No branches or pull requests

3 participants