Skip to content

Latest commit

 

History

History
22 lines (17 loc) · 1.01 KB

File metadata and controls

22 lines (17 loc) · 1.01 KB

Standard Operating Procedure: Location Reference Cache

Change management

  1. All authoritative location edits land in Location MDM (never direct Redis writes).
  2. MDM publishes LocationChangedEvent to RabbitMQ exchange location.events.
  3. Invalidation listener deletes site keys and walks org SET membership for scoped events.

Incident: elevated MDM load

  1. Check Redis availability and hit ratio in metrics.
  2. Run POST /api/admin/cache/warm after MDM recovery.
  3. Verify hot-key L1 config matches traffic profile (location.hot-keys).

Incident: stale reads reported

  1. Confirm Rabbit listener LOCATION_RABBIT_LISTENER=true in environment.
  2. Inspect DLQ location.cache.invalidation.dlq for poison messages.
  3. Trigger scoped invalidation via admin simulate-change or manual Redis DEL.

Nightly operations

  • Scheduled warm job (location.batch.warm-cron, default 03:00) reloads all sites from MDM.

Key rotation

  • Redis key version suffix :v1 — bump only with coordinated app deploy and warm job.