Repository navigation
Memory stream queue dequeue intermittently exceeds 30s response deadline (symptom of cluster-wide Orleans call timeouts) #5298
Description
What is failing
The Orleans memory-stream pulling agent's periodic read of queue memory-5-0xA0000005 timed out: the IMemoryStreamQueueGrain.Dequeue call between pods (10.244.5.235 → 10.244.2.157) exceeded the 30s response deadline, and MemoryAdapterReceiver.GetQueueMessagesAsync surfaced it through the agent's retry executor. This is an Orleans framework log site (Orleans.Streams.Memory), not application code.
Probable cause
Most likely a symptom of cluster-wide slow/pod-to-pod call latency or grain queue contention rather than a defect in the memory stream provider itself — the same window shows many sibling TimeoutException incidents across unrelated Orleans components (MessageHub, RoutingGrain, ActivityTracking, other memory-N queues), which points to general request-path pressure (CPU saturation, silo-to-silo messaging delays) rather than a fault in MemoryAdapterReceiver. Confidence: medium; a single occurrence with no inner exception or further stack cannot confirm it.
Impact
One occurrence on one pod (memex-portal-deployment-5c99d79997-xs87x) at 2026-09-22 19:13 UTC. The pulling agent retried and no message loss is indicated. Low standalone impact; its significance is as one data point in the broader timeout family.
Known / duplicate
This burst was folded from incident Admin/_LogIncident/3a8dfa6d2e5c4d2d (same log site, 61 revisions) — that incident is the primary record for this symptom. If that one is already filed, close this ticket as a duplicate.
Where to look
Orleans.Streaming/MemoryStreams/MemoryAdapterReceiver.cs(GetQueueMessagesAsync, line 45 in the frame)Orleans.Streaming/PersistentStreams/PersistentStreamPullingAgent.cs(ReadFromQueue)- Cluster health around firstSeen: check CPU/memory pressure and silo-to-silo latency on the memex pods.
Evidence
| Fingerprint | 4a95a54311e22598 |
| Category | Orleans.Streams.Memory |
| Severity | Error |
| Exception | System.TimeoutException |
| Namespace | memex |
| Pods | memex-portal-deployment-5c99d79997-xs87x |
| Occurrences | 1 |
| First seen | 2026-09-22 19:13:09Z |
| Last seen | 2026-09-22 19:13:09Z |
| Routing | not determined — no configured route matches the category Orleans.Streams.Memory. 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-09-22 19:13:09Z memex-portal-deployment-5c99d79997-xs87x fail: Orleans.Streams.Memory[103312]
Exception while retrying the 0th time reading from queue memory-5-0xA0000005
System.TimeoutException: Response did not arrive on time in 00:00:30 for message: Request [S10.244.5.235:11111:149102958 sys.svc.stream.agent/10.244.5.235:11111@149102958+Memory_2_memory-5-0xA0000005]->[S10.244.2.157:11111:149103361 memorystreamqueue/be8eb06fb4887559050000a005000000] Orleans.Providers.IMemoryStreamQueueGrain.Dequeue(System.Int32) #374A14BEFB3642A9.
at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
--- End of stack trace from previous location ---
at Orleans.Providers.MemoryAdapterReceiver`1.GetQueueMessagesAsync(Int32 maxCount) in /_/src/Orleans.Streaming/MemoryStreams/MemoryAdapterReceiver.cs:line 45
at Orleans.Streams.PersistentStreamPullingAgent.ReadFromQueue(QueueId myQueueId, IQueueAdapterReceiver rcvr, Int32 maxCacheAddCount, CancellationToken cancellationToken) in /_/src/Orleans.Streaming/PersistentStreams/PersistentStreamPullingAgent.cs:line 572
at Orleans.Internal.AsyncExecutorWithRetries.ExecuteWithRetriesHelper[T](Func`2 function, Int32 maxNumSuccessTries, Int32 maxNumErrorTries, TimeSpan maxExecutionTime, DateTime startExecutionTime, Func`3 retryValueFilter, Func`3 retryExceptionFilter, IBackoffProvider onSuccessBackOff, IBackoffProvider onErrorBackOff, CancellationToken cancellationToken) in /_/src/Orleans.Core/Async/AsyncExecutorWithRetries.cs:line 241
Re-addressed by the current identity function: this incident inherited 3a8dfa6d2e5c4d2d (Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.
Opened automatically from Admin/_LogIncident/4a95a54311e22598. Recurrences are folded into this issue rather than opening new ones.
Activity
systemorph-com commentedon Sep 22, 2026
Still occurring: 2 more since the last update (3 total).
memex-portal-deployment-5c99d79997-xs87x,memex-portal-deployment-5c444645f8-8pdzbRecent log lines
Re-addressed by the current identity function: this incident inherited
3a8dfa6d2e5c4d2d(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.rbuergi commentedon Sep 23, 2026
Duplicate of #4802.
Same code site: the Orleans memory-stream reader,
PersistentStreamPullingAgent.ReadFromQueue→MemoryAdapterReceiver.GetQueueMessagesAsync→IMemoryStreamQueueGrain.Dequeueon a queue grain hosted by another silo.This issue's own discriminator: memex 19:13:09Z, pod
5c99d79997-xs87x, queuememory-5, 30 sTimeoutException. The event behind it: the target10.244.2.157:…:149103361is the incarnation of7qdb4from before its restart. Both memex pods showrestarts: 1and booted at 19:15:01Z / 19:15:07Z.The reader recovers without help. In decompiled
Orleans.Streaming10.3.1,PumpQueueretriesReadFromQueueup to 6 times with backoff, and if it gives up, the agent's grain timer starts a new pump on its next tick. This issue's samples show noGiving up readingline. What is lost is the RAM-resident queue content on the silo that left or stalled, which is the structural exposure #4802 tracks (theAddMemoryStreamsretirement order is recorded there). The full per-issue table is on #4802.systemorph-com commentedon Sep 23, 2026
Left closed — this ticket was closed as NOT PLANNED, which is a decision rather than a claim that the fault stopped. The occurrences below are recorded here; if the decision should change, that is a person's call and not a recurrence's.
Still occurring: 2 more since the last update (5 total).
memex-portal-deployment-5c99d79997-xs87x,memex-portal-deployment-5c444645f8-8pdzb,memex-portal-deployment-777677694-d4j8c,memex-portal-deployment-777677694-hjkc8Recent log lines
Re-addressed by the current identity function: this incident inherited
3a8dfa6d2e5c4d2d(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.systemorph-com commentedon Sep 23, 2026
Left closed — this ticket was closed as NOT PLANNED, which is a decision rather than a claim that the fault stopped. The occurrences below are recorded here; if the decision should change, that is a person's call and not a recurrence's.
Still occurring: 4 more since the last update (9 total).
memex-portal-deployment-5c99d79997-xs87x,memex-portal-deployment-5c444645f8-8pdzb,memex-portal-deployment-777677694-d4j8c,memex-portal-deployment-777677694-hjkc8Recent log lines
Re-addressed by the current identity function: this incident inherited
3a8dfa6d2e5c4d2d(Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.