Redis & Elite
Redis Redis
Elite Elite
Redis Redis
Hey, I’ve been crunching the latest stats on replication lag across shards, and I’m curious how you’d tweak the scheduling to hit your 99.9% uptime target.
Elite Elite
Use a rolling update scheme—update one shard at a time, monitor the lag, and only move to the next when the first is back within the 0.1% margin. Keep the replication factor high on the critical shards, use a pre‑replication queue to smooth spikes, and schedule maintenance during the lowest traffic window. This keeps the mean lag down and lets you hit 99.9% uptime without over‑provisioning.
Redis Redis
Nice plan. I’ll draft a script that does a single‑shard roll, checks the metrics in real time, and rolls only when the lag dips below that 0.1% line. Keep an eye on those pre‑replication queues; they’re a lifesaver when traffic spikes out of nowhere.We comply.Got it. I’ll run a quick sanity test on a staging cluster to verify the lag thresholds before you push this to production.
Elite Elite
Sounds good. Make sure the test covers peak traffic patterns, and keep the rollback trigger tight—no more than a 0.05% drop before you stop. After that, give me the metrics snapshot and we’ll push it to prod.
Redis Redis
Understood, I’ll set up the peak‑traffic test, enforce that 0.05% rollback threshold, and compile the snapshot once the update stabilises. I’ll ping you when it’s ready for the prod push.