-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Failed to refresh slots cache #474
Labels
Comments
Sound reasonable. Care to make a PR? |
can do.. any preferences what you'd like the option called so it keeps with your option naming? else maybe just refreshSlotsTimeout (on the main cluster config/options) |
|
@shaharmor Sounds good to me. |
Released with v3.1.0 🍻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
yep, have read the other issues.. we are using AWS redis CLUSTER and it does work fine after the initial attempts.. our issue is we are seeing Failed to refresh slots cache the first time our scripts run because of a low timeout (we are connecting to multiple redis stores for different purposes which may be contributing to needing a slightly higher timeout)
https://github.com/luin/ioredis/blob/master/lib/cluster/index.js#L585-L612
the slots command being issued has a hardcoded 1,000ms timeout which doesn't seem to be enough in some cases. Modifying the timeout in node_modules... to 10,000ms rids the error but doesn't work for our deployment scenario unless we fork the module so just wondering if we can get a config variable for this timeout?
The text was updated successfully, but these errors were encountered: