Thomas Tosik

I tested it out this time with `resolveDns=False`. No change in the behaviour. I have to talk with Ops about the DNS caching. Will come back to you. When i...

So our Ops says there should not be any DNS caching issue. Also we can run the system in the broken state for days and nothing happens. Is there any...

So i decided to tap into the [events](https://github.com/StackExchange/StackExchange.Redis/blob/main/docs/Events.md) of the redis connection and log everything out. Ips of Redis and Sentinels before deleting Redis pod "rfr-redisfailover-persistent-0 " ``` ~$ kubectl...

Recently our Ops updated the systems from Ubuntu 18 to 20. No change in behaviour.

@lord-kyron: Sadly no. We recently updated several componets (Redis, Operator and Nuget) and i wanted to test if this helps. Have to find time for a test. A possible workaround...

@jchowdown: Did you have any success? I am in a similiar situation. But not on AWS but self-hosted Kubernetes.

We have also this problem since updating to 6.0.400 with the dotnet build command. Workaround with using "," instead of ";" worked for us.

How can i opt-out of this bevaviour or force my values? Before these changes there was no attribute what so ever (so the default behaviour of STJ i assume). Then...

@JotaDobleEse: Sadly no, we are fairly up-to-date on all of our components in our tests: Kubernetes, OS, Alpine 3.17 Container, DotNet 7, this lib itself, different cloud providers (custom, aws,...

I made a clean new test with StackExchange.Redis 2.6.90. My connection string is the following: "rfs-redisfailover-persistent.redis.svc.cluster.local:26379,abortConnect=false". Since resolveDns is not set it defaults to false. The result is still the...