How to fix NOREPLICAS Not enough good replicas to write in Redis

RedisINTERMEDIATEHIGHUpdated Dec 29, 2025· 185 views

The "NOREPLICAS Not enough good replicas to write" error occurs when a Redis master instance rejects write operations because insufficient replicas are available or synchronized. This is a replication safety feature that prevents data loss.

Quick fix

Fixes NOREPLICAS

redis-cli -h <master-host> -p <master-port> INFO replication
  1. Check the current replica status
  2. Verify replica connectivity
  3. Temporarily reduce the replica requirement
  4. Fix replica connectivity issues
redis — error
redis-cli -h <master-host> -p <master-port> INFO replication
NOREPLICAS Not enough good replicas to write

What this error means

This error is triggered by Redis's data safety mechanism when writing to a replicated Redis deployment. The master instance maintains a minimum replica threshold (configured via min-replicas-to-write and min-replicas-max-lag) to ensure data durability. When the number of synchronized replicas falls below the required threshold, or when connected replicas have excessive replication lag, the master refuses new write operations and returns the NOREPLICAS error. This protects against split-brain scenarios and limits the window of potential data loss. Without this safeguard, writes could be accepted by the master but lost if it crashes before replicating them to surviving replicas.

Typical symptoms

  • Write operations fail with the error message "NOREPLICAS Not enough good replicas to write"
  • Client applications receive a connection error when attempting to insert or modify data
  • Some write commands succeed intermittently while others consistently fail
  • Redis replicas appear offline or have high replication lag (slow to sync from master)
  • Error occurs shortly after starting Redis in a replication setup with restrictive replica requirements

Common causes

  1. One or more Redis replica instances are offline or disconnected from the master, reducing the count below the configured minimum
  2. Replica instances have excessive replication lag exceeding the configured max-lag threshold (network issues, slow replicas, or high write volume)
  3. Replica synchronization (SYNC/PSYNC) is in progress and not yet complete
  4. AUTH configuration is incorrectly set on replicas, preventing successful authentication and replication
  5. Network connectivity issues between master and replicas causing heartbeat failures or timeouts
  6. Kubernetes node recycling or pod restarts reducing the number of available replica instances temporarily

How to fix "NOREPLICAS Not enough good replicas to write"

1Check the current replica status

Connect to your Redis master and inspect the replication status to identify disconnected or lagged replicas:

bash
redis-cli -h <master-host> -p <master-port> INFO replication

Look for:
- role:master - Confirms you are on the master
- connected_slaves - Number of currently connected replicas
- slave0, slave1, etc. - Details for each replica including offset and lag

If connected_slaves is less than your min-replicas-to-write setting, that is your problem.

2Verify replica connectivity

Check if replicas can reach the master and authenticate properly:

bash
# On each replica, verify it can connect to the master
redis-cli -h <master-host> -p <master-port> PING

# Check the replica's replication status
redis-cli -h <replica-host> -p <replica-port> INFO replication

Look for master_link_status:up on replicas. If it shows down, the replica cannot sync.

If replicas fail to authenticate:
- Verify AUTH credentials are identical on master and replicas
- Check that masterauth is set correctly in replica config

3Temporarily reduce the replica requirement

To recover write access immediately while investigating, reduce the minimum replica threshold (use with caution):

bash
redis-cli -h <master-host> -p <master-port> CONFIG SET min-replicas-to-write 0

This disables the replica requirement temporarily. Writes will be accepted even if replicas are down, but you lose replication safety.

After fixing underlying issues, restore the setting:

bash
redis-cli -h <master-host> -p <master-port> CONFIG SET min-replicas-to-write 1

For persistence, update redis.conf:

bash
min-replicas-to-write 1
min-replicas-max-lag 10
4Fix replica connectivity issues

Once you have reduced the replica requirement, address the root cause:

For disconnected replicas:
- Restart the replica instance with the redis-cli SHUTDOWN command, then start it again
- Verify network connectivity between master and replica
- Check firewall rules allowing TCP communication on the Redis port

For replicas with excessive lag:
- Check replica resource usage (CPU, memory, disk I/O) - upgrade if necessary
- Verify network bandwidth between master and replicas
- Reduce master write load if possible
- Increase min-replicas-max-lag if brief lag spikes are acceptable:

bash
redis-cli -h <master-host> CONFIG SET min-replicas-max-lag 20
5Restore safe replication settings

Once all replicas are healthy and connected:

bash
# Verify all replicas are in sync
redis-cli -h <master-host> -p <master-port> INFO replication

# Set appropriate thresholds for your deployment
# Require at least 1 replica with lag <= 10 seconds
redis-cli -h <master-host> CONFIG SET min-replicas-to-write 1
redis-cli -h <master-host> CONFIG SET min-replicas-max-lag 10

# For Kubernetes deployments with multiple replicas:
redis-cli -h <master-host> CONFIG SET min-replicas-to-write 2
redis-cli -h <master-host> CONFIG SET min-replicas-max-lag 10

Persist these settings in your redis.conf or ConfigMap.

Advanced notes

Configuration Details:
- min-replicas-to-write (formerly min-slaves-to-write): Number of replicas that must acknowledge writes. Default: 0 (disabled).
- min-replicas-max-lag (formerly min-slaves-max-lag): Maximum replication lag in seconds. Default: 10 seconds.

Kubernetes/Container Deployments:
In Kubernetes with Redis Helm charts, NOREPLICAS errors often occur during node recycling when replicas are temporarily unavailable. Solutions include:
- Setting min-replicas-to-write 0 if write availability is more important than replication safety
- Using pod disruption budgets to ensure at least one replica is always running
- Increasing timeouts and lag thresholds during infrastructure maintenance windows

AWS ElastiCache:
If using AWS ElastiCache for Redis, check the "Replication" tab in the console to see replica health and sync status. Ensure automatic failover is configured if you want master promotion during outages.

Large Datasets:
With very large datasets (50GB+), initial replication sync can take many seconds. Increase min-replicas-max-lag accordingly or temporarily disable the check during initial setup.

Frequently asked questions

What does "NOREPLICAS" mean?
This error is triggered by Redis's data safety mechanism when writing to a replicated Redis deployment. The master instance maintains a minimum replica threshold (configured via min-replicas-to-write and min-replicas-max-lag) to ensure data durability. When the number of synchronized replicas falls below the required threshold, or when connected replicas have excessive replication lag, the master refuses new write operations and returns the NOREPLICAS error.
How do I fix "NOREPLICAS"?
The "NOREPLICAS Not enough good replicas to write" error occurs when a Redis master instance rejects write operations because insufficient replicas are available or synchronized. This is a replication safety feature that prevents data loss.
What causes "NOREPLICAS"?
One or more Redis replica instances are offline or disconnected from the master, reducing the count below the configured minimum Replica instances have excessive replication lag exceeding the configured max-lag threshold (network issues, slow replicas, or high write volume) Replica synchronization (SYNC/PSYNC) is in progress and not yet complete
Is the "NOREPLICAS" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading