-
Notifications
You must be signed in to change notification settings - Fork 12
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
Busy loop at disconnect #66
Comments
Thank for the report. |
Thanks for the quick response. I would suggest smth. like: |
I mean it has to be implemented! |
Hey, do you have any plans to add this soon? |
Hello, I'm working on it! |
Cool, not yet so firm in rust, but I can at least do some manual testing... :) |
Thanks, works like a charm! |
If you don't set the |
I didn't set that... let mut c : rustis::client::Config = config.into_config().unwrap();
c.reconnection = rustis::client::ReconnectionConfig::Exponential {
max_attempts: 0,
min_delay: 100,
max_delay: 8000,
multiplicative_factor: 2,
jitter: 50
};
c.command_timeout = Duration::from_secs(1); Without the command_timeout it seems to block/wait, till connection is established again (and the command is successful once established again). |
Ok, I'm going to take a look at it |
Should be fixed in 012a123 |
Hey, first, thanks for the lib, much appreciated!
I did a connect to redis like this:
let redis_cli = Client::connect("127.0.0.1:6379").await;
which works just fine, if the redis server is running.
But if I kill redis (while still connected), I get error spamming in the console
Is there some way around this?
Not sure how the reconnect logic is for that case, but it seems like a busy loop?
The text was updated successfully, but these errors were encountered: