Fair point. I'll definitely consider co-primes the next time I deploy a system with complicated scheduling.
- timeout: 1m
- expireInterval: 1m
- updateInterval: 5m
- etc
The first thing I do is go in and change them all to - timeout: 59s
- expireInterval: 61s
- updateInterval: 307s
- etc
and then see what the new "problem interval" is. It's either gone, because the spike was from contention from all 3 jobs running every 5 minutes, or the new problem occurs now at 61s intervals.