Layout area rendering fails with DeliveryFailureException when placement of the tenant messagehub grain times out

Chiusa
  • Qualcosa non va?
#6,394 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
18/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend, distributed-systems

Direzione di ricerca

Start with MeshWeaver.Layout.Composition.LayoutAreaHost at the log site "Rendering failed for area" and the message-hub delivery it awaits, then the Orleans PlacementService.PlacementWorker timeout frames the issue links from the Ops/Logs entries. The open question is whether this is a residual of #5037 on the messagehub grain family, so the first check is the placement-timeout log query for messagehub over the days since the Oct 2–4 rechecks. Done means that question is answered with evidence, either as a duplicate of #5037 or as a new root cause.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug sev:M

What is failing

Rendering the Overview layout area in the memex portal aborts with a DeliveryFailureException: the delivery to the tenant message hub TelefonicaSeguros fails because Orleans cannot place the grain messagehub/TelefonicaSeguros within the 30-second placement timeout. The user sees the area render fail instead of a page.

Probable cause

A transient Orleans placement-worker stall placing the tenant messagehub grain. Confidence: moderate — there is a single sample and no deeper stack, so what stalled the placement (silo load, placement-director contention, catalog pressure) is unclear from this evidence alone.

This is the same failure class as #5037 (grain placement timeouts on memex/memex-cloud). The September investigation trail recorded messagehub grains timing out during placement alongside the routing/default bursts (see Ops/Actions/logs-5037-cloud-placement-context-20260928 and the landed Ops/Logs entries from 2026-09-26/28), while the post-roll rechecks for #5037 (Oct 2–4) verified only routing/default timeouts. This incident may therefore be a residual of #5037 on the messagehub grain family that the fix did not cover — treat as a possible duplicate until that is ruled out.

Impact

One occurrence on one portal pod, one tenant's Overview area. A user-visible but retryable render failure; low volume, no data loss indicated.

Where to look

  • The render/delivery path: MeshWeaver.Layout.Composition.LayoutAreaHost (log site "/Rendering failed for area") and the message-hub delivery it awaits.
  • Orleans PlacementService.PlacementWorker — the placement timeout lines and stacks landed in Ops/Logs from the 2026-09-28 #5037 classification runs show the worker's GetOrPlaceActivation/AddressWaitingMessages frames.
  • The telefonicaseguros tenant space's messagehub grain on the aks-silos nodes.

Suggested first check: re-run the #5037 log query against the messagehub grain family (Grain placement operation timed out for grain messagehub) over the days since the Oct 2–4 rechecks to establish whether this is one stray or a recurring residual.

Evidence
Fingerprint 8a6d880f930298f9
Category MeshWeaver.Layout.Composition.LayoutAreaHost
Severity Error
Exception MeshWeaver.Messaging.DeliveryFailureException
Namespace memex
Pods memex-portal-deployment-845898d964-ptszc
Occurrences 1
First seen 2026-10-09 20:42:07Z
Last seen 2026-10-09 20:42:07Z
Routing not determined — no configured route matches the category MeshWeaver.Layout.Composition.LayoutAreaHost. This repository is the configured fallback, not a finding about who owns the fault; the category names the LOGGER, which may not be the subject.
Recent log lines 
2026-10-09 20:42:07Z memex-portal-deployment-845898d964-ptszc fail: MeshWeaver.Layout.Composition.LayoutAreaHost[0]
      Rendering failed for area Overview
      MeshWeaver.Messaging.DeliveryFailureException: Delivery to 'TelefonicaSeguros' failed: Grain placement operation timed out for grain messagehub/TelefonicaSeguros.

Opened automatically from Admin/_LogIncident/8a6d880f930298f9. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site a11c38b604d38f67: other fingerprints of this site fold in here as comments rather than opening tickets of their own.

Lingua principale
C#
Stelle
12
Fork
5
Merge medio
5h 10m
PR unite (30g)
979

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Systemorph/MeshWeaver

Tutte le issue di Systemorph/MeshWeaver

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.