Closed KendoSai closed 4 months ago
Updates: looks like this issue is relevant to our network and Istio usage in our Kubernetes cluster.
I used this annotation to exclude the 26379 and 6379 port and this issue stopped happen since this afternoon
traffic.sidecar.istio.io/excludeOutboundPorts: "26379,6379"
https://istio.io/latest/docs/reference/config/annotations/#SidecarTrafficExcludeOutboundPorts
=> The issue still happened this morning, so it's not a correct fix.
Updated: we have tried disable Istio for this service and the issue has gone.
I'll be honest: I have no idea what that means, but: I'm glad you found the problem. I wouldn't have stood a chance.
Thanks @mgravell, I'll close this issue then
Hi @mgravell, I'm using StackExchange.Redis 2.7.17 to connect to Redis Sentinel and facing this strange issue
There is a service with 8 pods running on Kubernetes, sometimes when there is a new deployment that spinned up a new service's pods, there will be 1 pod got this exception "Sentinel: The ConnectionMultiplexer is not a Sentinel connection. Detected as: Standalone". Currently we have to fix it manually by deleting this 'fault' pod, when new pod is intialized, the error is gone
Our connection strings are:
kala-c1redis-01.abc.lc:26379;kala-c1redis-02.abc.lc:26379;kala-c1redis-03.abc.lc:26379
I have put the logger into theConnectionMultiplexer.Connect(options, writer);
and here is the logDo you have any ideas on this?
Here is the RedisCacheClient code