Graham McIntire
1f021f42e6
Both `prop` and `prop-backfill` deployments use `app=prop` for the libcluster selector, so they share a :global namespace. During a rollout the backfill pod can win FCFS leader election and end up running the real-time MQTT client on the same pod that's churning through batch enrichment jobs. Worse, the backfill pod was still running the pre-IPv4-fix image and surfacing :einval on every 30-second retry. Gate `pskr_mqtt_enabled` off when PROP_ROLE=backfill. Explicit PSKR_MQTT_ENABLED=true still wins if you ever want to flip it on for a dedicated MQTT pod. |
||
|---|---|---|
| .. | ||
| config.exs | ||
| dev.exs | ||
| prod.exs | ||
| runtime.exs | ||
| test.exs | ||