Unable to reconnect to Redis Cluster in Kubernetes after cluster rollout about fred.rs HOT 12 CLOSED

Hey @aembke, any updates on this or any assistance we can provide? Not having this is causing us some grief in production.

from fred.rs.

We've reverted to using the redis-rs library with a non-clustered Redis for the time being.

from fred.rs.

Yeah, good find @zombiezen. This is one of the reasons why the next release will be a major release. The changes necessary to the connection management plumbing are too invasive to do in a patch or minor release, but they're required to fix this issue.

I'm about halfway through those changes now, and my goal is to release them by the end of the month or shortly after.

from fred.rs.

I've been using fred at this commit for a few weeks: 36798a2 and I'm not encountering this problem anymore, maybe @zombiezen can check too?

from fred.rs.

Out of curiosity - would you find it useful to override DNS resolution logic? I've been debating whether to expose an interface for doing this (similar to hyper).

from fred.rs.

Thanks! LMK if there's anything else I can do to help in a fix. We have some workarounds for this, but it would definitely save us some operational headaches to have it addressed.

AFAIK we don't need anything fancy for DNS resolution logic: the OS-provided resolver is fine for us.

from fred.rs.

Sounds good. This is definitely a use case I plan on supporting, and I'll keep you updated on the status of the fix.

from fred.rs.

Yeah my apologies, getting back into it now. There's a couple PRs folks have submitted that I think are related to this. I'll take a look at the options and go with the fastest one that addresses this.

from fred.rs.

@zombiezen Curious if you have any workaround in production?

from fred.rs.

We're working on a new service in rust and have chosen fred for it; the main reason why it was chosen is that it's the only redis library that does async, pooling, and clustering (all at the same time). We're also running into this exact problem & looking forward to trying out the next major release, thanks all.

from fred.rs.

Quick update to the folks on this thread - I just published 6.0.0-beta.1 to crates.io. It has an entirely new implementation of the cluster interface and the repros I had for this issue seem to work now with the new version. If you have any feedback on the new interface please let me know.

from fred.rs.

I've been using fred at this commit for a few weeks: 36798a2 and I'm not encountering this problem anymore, maybe @zombiezen can check too?

I don't want to leave you hanging, but we've since reverted to a sharded REDIS system. I don't think will have time to verify this bug. At least not in our immediate roadmap.

Thanks for the patch though.

from fred.rs.