Alec Embke

Hey @allada, did you have any luck repro'ing this on your side? I added sentinel support to the failover testing tool I usually use for this kind of thing (https://github.com/aembke/fred.rs/tree/main/bin/inf_loop)...

Interesting, is that where the logs end? Or was there anything after that? If I'm reading that correctly the decoder gets 87 bytes from the socket, but if the logs...

Interesting, how many clients are you using in total? Or if you're using a pool what's the pool size?

Huh, that doesn't quite add up so something might be wrong here. Some back of the napkin math: `sizeof::() = 136 * 7 channels per client (this should probably change)...

Interesting, thanks for looking into it already with dhat. Can you describe the use case a bit? How many messages are you receiving roughly per second/minute/whatever, how big are the...

Hi @bbeausej, could you provide a full rust code sample that reproduces this? I tried adding a test for this (https://github.com/aembke/fred.rs/blob/feat/9.1.0/tests/integration/sorted_sets/mod.rs#L772-L800) but haven't been able to repro the issue.

Closing for now, but let me know if you're able to repro this.

Can you show the `ReplicaConfig` that you used to repro the timeout? There are [integration tests](https://github.com/aembke/fred.rs/blob/main/tests/integration/other/mod.rs#L465-L491) for this that run without issues against a primary - replica pair when not...

Yeah that should work as well. When the client connects to the primary it calls `ROLE` to inspect any replicas, and if none are found it creates an empty replica...

There's a long thread about this in this redis-rs repo, and a link to a discord discussion with more info: https://github.com/redis-rs/redis-rs/issues/1228 Unfortunately I don't think there really is a solution...