From 1eee56d0baac40499dab2fa942b82397364fbb86 Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Tue, 26 May 2026 18:48:58 +0000 Subject: [PATCH] redis: tolerate up to 1KB of AOF tail corruption on load Post-2026-05-26 unclean node2 reboot left redis-v2-2's incremental AOF truncated at offset 84799139. With aof-load-corrupt-tail-max-size at its default 0, redis refuses to load any corruption and crashloops. Setting 1024 lets it truncate the corrupted tail and continue, which is the right call for a non-source-of-truth cache fronted by sentinel. Co-Authored-By: Claude Opus 4.7 --- stacks/redis/modules/redis/main.tf | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/stacks/redis/modules/redis/main.tf b/stacks/redis/modules/redis/main.tf index 7ff129bc..ee358b06 100644 --- a/stacks/redis/modules/redis/main.tf +++ b/stacks/redis/modules/redis/main.tf @@ -268,6 +268,12 @@ resource "kubernetes_config_map" "redis_v2_conf" { auto-aof-rewrite-min-size 128mb aof-load-truncated yes aof-use-rdb-preamble yes + # Allow loading an AOF with up to 1KB of garbage at the tail (post-2026-05-26 + # node2 unclean reboot corrupted redis-v2-2's incremental AOF at offset + # 84799139; without this, redis-v2-2 crashlooped). Redis truncates the + # corrupted tail and continues. Default is 0 (refuse to load any corruption). + aof-load-corrupt-tail-max-size 1024 + replica-read-only yes replica-serve-stale-data yes