Madelyn Olson

``` 22:S 08 Feb 2024 17:19:30.450 * Reconnecting to MASTER 10.244.164.132:6379 22:S 08 Feb 2024 17:19:30.450 # Error condition on socket for SYNC: Connection refused ``` This is fine, this...

> b48b97dc848d1b6c730261c1990e8334d5d3faed at 10.244.174.199:16379 failed: Connection refused for almost 20 seconds and only after that election got triggered. cluster-node-timeout is 15seconds. So, to make sure I understand this correctly. Everything...

Do you have other logs from the other masters? There is more information such as when the other masters indicated the other masters were dead which would be helpful in...

> this case, as it's 15 seconds, i expect redis cluster to trigger election immediately after 15 seconds, why was additional 6 seconds taken? for what? what more redis configurations...

> In the case of disk failure, the cluster node will exit immediately if there are some changes around the cluster. This adds more states we have to reason about,...

We'll move this to 9.0, we didn't quite implement this for 8.1 and this PR just needs a little bit more refinement.

Seems like a good idea to me as well.

> A replica in cluster should not possess any slot. Yeah, replicas are by design not supposed to own any slots. I would rather update the judgements to prevent the...

@hwware @enjoy-binbin I suppose the counter question I have is what is the specific use case here when we have the logs for when it actually started?

> We shouldn't recommend relying on logs, should we? Getting from INFO should be easy for clients. My concern was that if someone was concerned about a latency event that...