You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using this cache in conjunction with our Grafana Loki deployment handling roughly 100-200GB of uncompressed logs every day. This causes issues for the cache reading from master. The redis cluster handles the caching of compressed logs which should work to up to 100GB of throughput (well over the daily amount of 100GB uncompressed logs).
We hit a readiness probe failed error without any helpful error information
The error is as follows
I/O error reading bulk count from MASTER: No error information
RDB: 50 MB of memory used by copy-on-write
Reconnecting to MASTER xxx.xxx.xxx.xxx:6379 after failure
MASTER <-> REPLICA sync started
Non blocking connect for SYNC fired the event.
Master replied to PING, replication can continue...
Partial resynchronization not possible (no cached master)
The main issue for us is the No error information part
There is no way to debug this issue with this kind of response message
To reproduce
We use Kubernetes pods with the spotahome/redis-operator
The failover has some CustomConfig that will override the default values set by the operator (see below in additional information around CustomConfig).
We run 4 instances that have with 9 pod across them. We request 3 cores and 35GB of memory per pod
Expected behavior
We expect one of two scenarios to occur.
The pod to fail with an error message that can help us to change config to improve performance
The pod to either not fail the readiness probe or restart the pod on the occurrence of this error message (you might not be able to help with this one, as we use the redis-operator)
Additional information
We have the Persistent Volume Claim set to the size of 256GB. This should be more than enough data to hold the searched data for any timeframe.
CustomConfig set in the Redis Failover
Describe the bug
We are using this cache in conjunction with our Grafana Loki deployment handling roughly 100-200GB of uncompressed logs every day. This causes issues for the cache reading from master. The redis cluster handles the caching of compressed logs which should work to up to 100GB of throughput (well over the daily amount of 100GB uncompressed logs).
We hit a
readiness probe failed
error without any helpful error informationThe error is as follows
The main issue for us is the
No error information part
There is no way to debug this issue with this kind of response message
To reproduce
We use Kubernetes pods with the
spotahome/redis-operator
The failover has some CustomConfig that will override the default values set by the operator (see below in additional information around CustomConfig).
We run 4 instances that have with 9 pod across them. We request 3 cores and 35GB of memory per pod
Expected behavior
We expect one of two scenarios to occur.
Additional information
We have the Persistent Volume Claim set to the size of 256GB. This should be more than enough data to hold the searched data for any timeframe.
CustomConfig set in the Redis Failover
The text was updated successfully, but these errors were encountered: