How to fix ERR BGREWRITEAOF scheduled when RDB save in progress in Redis

# Check if a background save is in progress
redis-cli INFO persistence | grep -E "rdb_bgsave_in_progress|aof_rewrite_in_progress|rdb_last_bgsave_status"

# Monitor the RDB save progress (if in progress)
redis-cli INFO persistence | grep rdb_current_bgsave_time_sec

# Wait for completion, then verify the save finished successfully
redis-cli INFO persistence | grep rdb_last_bgsave_status

# View current save directives
redis-cli CONFIG GET save

# View AOF rewrite settings
redis-cli CONFIG GET auto-aof-rewrite-percentage
redis-cli CONFIG GET auto-aof-rewrite-min-size

# Example: Less frequent RDB saves (only when 1000 keys change in 300 seconds)
redis-cli CONFIG SET save "300 1000"

# Or disable automatic RDB saves entirely if you rely on AOF
redis-cli CONFIG SET save ""

#!/bin/bash

# Function to safely trigger BGREWRITEAOF
safe_bgrewriteaof() {
  local status=$(redis-cli INFO persistence | grep "rdb_bgsave_in_progress" | cut -d: -f2)
  if [[ "$status" == "0" ]]; then
    echo "No RDB save in progress, starting BGREWRITEAOF..."
    redis-cli BGREWRITEAOF
  else
    echo "RDB save in progress, skipping BGREWRITEAOF"
    exit 1
  fi
}

# Call the function
safe_bgrewriteaof

# Option 1: Use AOF-only persistence (more durable, but larger files)
redis-cli CONFIG SET appendonly yes
redis-cli CONFIG SET save ""

# Option 2: Use RDB-only persistence (faster restarts, point-in-time snapshots)
redis-cli CONFIG SET appendonly no
redis-cli CONFIG SET save "900 1 300 10 60 10000"

# Option 3: Increase system resources so persistence completes faster
# Check memory and disk I/O during saves
redis-cli INFO memory | grep used_memory_peak
iostat -x 1  # Monitor disk utilization