Redis [BUG] Sentinel fails to failover

Describe the bug

We have a redis sentinel setup with 3 redis instances and 3 sentinels. When the master redis node crashes and restarts, the cluster does not failover to another node. The log is flooded with the following:

2022-09-28 15:17:36.843 CEST1:S 28 Sep 2022 13:17:36.843 * Connecting to MASTER redis-sentinel-production-node-0.redis-sentinel-production-headless.redis-sentinel-production.svc.cluster.local:6379
Info
2022-09-28 15:17:36.844 CEST1:S 28 Sep 2022 13:17:36.844 * MASTER <-> REPLICA sync started
Info
2022-09-28 15:17:36.844 CEST1:S 28 Sep 2022 13:17:36.844 * Non blocking connect for SYNC fired the event.
Info
2022-09-28 15:17:36.887 CEST1:S 28 Sep 2022 13:17:36.887 * Master replied to PING, replication can continue...
Info
2022-09-28 15:17:37.163 CEST1:S 28 Sep 2022 13:17:37.163 * Trying a partial resynchronization (request 46949757047a51b19b4d5f534ba14c4fd5757abf:281092860).
Info
2022-09-28 15:17:37.450 CEST1:S 28 Sep 2022 13:17:37.449 * Master is currently unable to PSYNC but should be in the future: -LOADING Redis is loading the dataset in memory
Info
2022-09-28 15:17:37.852 CEST1:S 28 Sep 2022 13:17:37.852 * Connecting to MASTER redis-sentinel-production-node-0.redis-sentinel-production-headless.redis-sentinel-production.svc.cluster.local:6379

since we have a large rdb/aof it can take serval minutes in order to start the instance, meanwhile our cluster is down for writes since a failover is not triggered.

To reproduce

N/A

Expected behavior

I would expect the failover to start.

Additional information

Any additional information that is relevant to the problem.

Comment From: hwware

Could you please provide your redis versionn number and redis instance and redis sentinel config. Thanks, Or more logs of them

Comment From: moticless

@MikkelSnitker, can you update please?