We're seeing the same issue posted here:
#2577
StackExchange.Redis.RedisConnectionException: Unexpected response to HMGET: Integer: 1
Triggered when calling HashGetAsync and when the app is running OOM. App is running on k8s in a container with a mem limit.
StackExchange.Redis version: 2.7.17 on .NET 8, Asp.NET Core application.
Difficult to reproduce, it seems to happen when the application is close to the container mem limit. We see this happen alongside System.OutOfMemoryExceptions.
Additionally, (and much scarier) behavior is we're also occasionally getting the wrong value on GETs in this state. E.g. We check the cache for key:123, but the data we get back is what we expect for key:234. We're not sure if it's the GET returning the wrong data or if the initial SET was setting the wrong data.
We're seeing the same issue posted here:
#2577
Triggered when calling
HashGetAsyncand when the app is running OOM. App is running on k8s in a container with a mem limit.StackExchange.Redis version:
2.7.17on .NET 8, Asp.NET Core application.Difficult to reproduce, it seems to happen when the application is close to the container mem limit. We see this happen alongside System.OutOfMemoryExceptions.
Additionally, (and much scarier) behavior is we're also occasionally getting the wrong value on GETs in this state. E.g. We check the cache for
key:123, but the data we get back is what we expect forkey:234. We're not sure if it's the GET returning the wrong data or if the initial SET was setting the wrong data.