Graham McIntire
a6a2c859b4
All app=prop pods (hot + backfill) join the libcluster cluster and are eligible to win Oban leader election. The backfill pod's Cron plugin is configured with crontab: [], so when it wins, every cron silently stops firing until the leader peer entry expires and rotates. Today's deploy showed the failure mode: backfill won the post-restart election, all crons (PSKR calibration, propagation grid, partition maintenance, etc.) were silent for 75 minutes until I bounced the backfill pod manually. Setting `peer: false` on the backfill role makes it ineligible for leadership entirely. Hot pods compete only with each other. |
||
|---|---|---|
| .. | ||
| config.exs | ||
| dev.exs | ||
| prod.exs | ||
| runtime.exs | ||
| test.exs | ||