# SENTINEL: failover aborted - no good replica found for master 'mymaster'

- **ID:** `redis/sentinel-failover-no-good-replica`
- **Domain:** redis
- **Category:** runtime_error
- **Error Code:** `SENTINEL`
- **Verification:** ai_generated
- **Fix Rate:** 80%

## Root Cause

Sentinel could not promote any replica because all replicas are either stale (data too old), down, or have priority 0.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| redis 6.2 | active | — | — |
| redis 7.0 | active | — | — |
| redis 7.2 | active | — | — |

## Workarounds

1. **Check replica replication lag and priority:
INFO REPLICATION on each replica
Ensure at least one replica has lag < sentinel-replica-down-after-milliseconds and priority > 0.
If lag is high, wait for sync or manually trigger replication from master.** (85% success)
   ```
   Check replica replication lag and priority:
INFO REPLICATION on each replica
Ensure at least one replica has lag < sentinel-replica-down-after-milliseconds and priority > 0.
If lag is high, wait for sync or manually trigger replication from master.
   ```
2. **Adjust replica priority to 1 (default) on all replicas:
CONFIG SET replica-priority 1
This ensures they are eligible for promotion.** (90% success)
   ```
   Adjust replica priority to 1 (default) on all replicas:
CONFIG SET replica-priority 1
This ensures they are eligible for promotion.
   ```

## Dead Ends

- **** — Timeout increase does not fix stale or down replicas; failover will still abort. (65% fail)
- **** — If the replica is too stale, promoting it can cause data loss and inconsistency. (75% fail)
- **** — Restarting sentinels does not change replica state; they will still see the same condition. (80% fail)