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

クローズ
  • 何か問題がありますか？
#6,394 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
18/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
活発
技術スタック
csharp
領域
backend, distributed-systems

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
C#
スター
12
フォーク
5
平均マージ
5時間 18分
マージ済み PR（30日）
917

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Systemorph/MeshWeaver のほかの issue

Systemorph/MeshWeaver の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。