İki hafta önce fixlediğimiz "tükendi pushu" 32 kez yine buzzed — claim contention bypass (PR #654 VIII F3)

Antalya Lara da 44 yaslarinda "Lara Manti Evi" sahibi Gulizar, 4 yil boyunca yaz turistik yogunlugu yasamisti. PR #644 batch V F3 ten sonra (3 hafta once shipped auto-86 push debounce fix) iki haftadir phone una tek bir "Manti tukendi" pushu geliyordu, 14 degil. Cok memnundu. Ama Cuma 21:30 dinner rush ta Apple Watch titremeye basladi: 32 ping in 5 minutes. Manager Cemal in Galaxy Watch unda da 32. "Manti 30 dakika once tukendi, niye 30 push?" Forensik: 32 concurrent order POST manti iceriyordu (yaz tatil rush). Ilk 6 order parallel hit; stock_qty atomic UPDATE birinci ye yes (stock=0), digerlerine no. Ama 6 si da catch branch e dustu cunku 21:25-21:35 window unda **5 farkli cron job ayni anda** cron_idempotency_claims INSERT yapiyordu: aff-auto-suspend + pos-retry + email-drips + webhook-retry + feedback-sentiment (her 30dk cron, xx:00 + xx:30 fire). Lock contention spike; D1 SQLITE_BUSY throw; order POST catch branch fire-anyway path; **de-dup BYPASS**. V F3 nin catch comment u: "operator notification trumps de-dup hygiene" — high-velocity alert class larinda (out-of-stock, table-occupied, queue-full) bu spam a donusur. **PR #654 batch VIII F3** fix tek satir: catch branch i SUPPRESS (return) + structured BEACON prefix [BEACON:auto86_claim_insert_failed] + console.warn. Cloudflare Logpush + Sentry alert rule prefix e pinned; sustained contention internal ops team e alert. Backstop signal verify: (1) operator dashboard "Stok Durumu" widget 30sn refresh, stock_qty <= 0 anlik gosterir; (2) daily 09:00 UTC low-stock-digest email cron daily threshold (5 urun, 24h tukenenler). **Deeper fix cron schedule rebalance**: dispatcher handleScheduled icinde minute offsets — aff-auto-suspend xx:00, pos-retry xx:05, email-drips xx:10, webhook-retry xx:15, feedback-sentiment xx:20, status-snapshot xx:25. "5 simultaneous" pattern her 30dk slot ta kirildi; hala 30dk frequency ama staggered. Lock contention spike artik tek cron firing zamaninda olmaz. Gulizar Cuma akssm sonraki dinner rush ta **tek bir manti-tukendi push** aldi. TripAdvisor mini-review guncelendi: "thMenu push spam i ikinci kez de duzeltti." 6-ay ucretsiz Pro tier upgrade. Pattern: **debounce / de-dup / rate-limit mekanizmasi ekledikten sonra, "de-dup mekanizmasi fail etse ne olur?" senaryosunu test et. Catch branch fail-open default sessiz spam vector u; high-velocity low-criticality alert lerde de-dup hygiene guaranteed delivery den onemlidir.** Implementation checklist: (1) her de-dup mekanizmasinda claim INSERT fail decision explicit, default fail-suppress; (2) alert class framing — high-criticality guaranteed delivery, low-criticality de-dup hygiene; (3) backstop signal verify; (4) structured BEACON prefix Logpush/Sentry pin; (5) cron schedule rebalance same-clock-tick fire lar lock contention spike yaratir, minute offset spread; (6) quarterly cron-contention metric review claim INSERT failure rate > 5%/5min alarm. Joao Porto Cervejaria do Cais versionunda francesinhas spam ile benzer flow.

İlgili makaleler