26 lines
984 B
Markdown
26 lines
984 B
Markdown
# Failover Timing Update — July 8, 2026
|
||
|
||
## Change
|
||
Per Germaine's direction, the failover timing was updated:
|
||
|
||
| Parameter | Before | After |
|
||
|-----------|--------|-------|
|
||
| Check interval | Every 10 min | Every 5 min |
|
||
| Confirmation sleep | 60s × 4 cycles | 30s × 4 cycles |
|
||
| Total confirmation window | ~3.5 min | ~2 min |
|
||
| Max downtime before failover | ~13.5 min | ~7 min |
|
||
|
||
## What was changed
|
||
1. **Cron on app1-bu:** `*/10 * * * *` → `*/5 * * * *`
|
||
2. **Watchdog script sleep:** `sleep 60` → `sleep 30` (line ~71)
|
||
3. **Confirmation message:** Updated from "~3.5 minutes" to "~2.0 minutes" (lines ~68, ~96)
|
||
|
||
## Rationale
|
||
Faster detection = shorter failover. 7 min max vs 14 min max. User prioritized speed over cost.
|
||
|
||
## DR Plan impact
|
||
DR-PLAN.md and server-inventory.md should be updated to reflect:
|
||
- Server is warm (always on), not cold (boot on demand)
|
||
- Check interval is 5 min, not 10 min
|
||
- Verification needs to check both the cron schedule AND the sleep value
|